yashsingh1/xdaforums huggingface dataset:
[Android General] DaemeonZane:
My advice on this is honestly to wait. I've noticed the same thing with R.T.P. and haven't figured out a good fix yet... truth is, I think it may have something to do with the device keeping things in a different area, etc... and I've noticed that root doesn't seem to be FULL root. When in recovery or FTM, even though I have root, I can't use root in an adb shell... BUT I HAVE GOTTEN TO FASTBOOT!!!!!! I'm gonna see if there's a way to pull just the recovery image and go from there....

For fastboot: If you have ADB you have fastboot, even if you don't know it yet. Make sure adb sees you device by running the following:

adb devices

adb reboot bootloader

Your device will have a RED light at the top, and your screen will be black. Make sure Windows Update can get drivers for you, and it'll install it.

Please verify on your phones if you can do the same, but you should be able to. If I can get a stock recovery.img, we've got CWM the same day... and if we can get CWM, we're closer to running custom ROM's.... as soon as I can get a fill image dump on this damn thing lol

-----------------------------------------------------------------------------------------------​

Found new info: mmcblk0p16 is our recovery partition. Stay tuned for a CWM touch recovery!!!
[Android General] Krsmqn:
This is great news!!! I have been in fastboot before and didn't know it. Have you been able to execute any fastboot commands to confirm it's operable? And can you link the driver? Super excited for a custom recovery.

Hats off to you
[Android General] DaemeonZane:
So.... I have a boot.img, a recovery.img, and a full /system tar... still working on cwm.... will upload when I get home
[Android General] DaemeonZane:
Ignore this post, i need my post count so i can upload external links n whatnot
[Android General] Krsmqn:
You did all this at work?
[Android General] DaemeonZane:
Ok, ladies n gents, the wait is somewhat over, at least for some almost stock info:

system.ext4.img - http://d-h.st/wwn

boot.img - http://d-h.st/XWT

recovery.img - http://d-h.st/0QI

The automatic recovery builder was disabled this morning and hasn't cranked out any new dev's since 12am last night, so I'm keeping an eye on it, but if I see nothing by in the morning, I'll just see about the manual config and try to make it happen.... these aren't truly flashable yet, but they'll give someone something to play with for awhile.... have fun Source fans!
[Android General] Krsmqn:
Updated OP.:good:

Attempting to build custom touch recovery.... using the above file. I'll post results for testing. Wish us luck!

... BUILD FAILED! ... wtf...

For anyone who wants to try a manual port of CWM Recovery, try this link.

.... or this.

.... or this link.

I do not have a linux computer so the latter option is out for me... not sure about the first.

If you want to try getting a Nandroid Backup, try this.

We are closer then ever though!
[Android General] Krsmqn:
This is using "Online Nandroid Backup" from the link in the post above.

"/BOOT NOT FOUND" & "/RECOVERY NOT FOUND" ..... ???

"consider installing a patch file for your device for a complete nandroid backup"

Uh ... what patch?
[Android General] DaemeonZane:
I'm working on exactly this, and actually used the same tool to pull that System Image lol I'm working on it in a kitchen right now to see what I can come up with, including a deodexed ROM and whatnot. I'm gonna try to make this happen for us, but anyone else willing to contribute to the work, let me know, so that we can work together and build this faster.... I'd like to, once we have a full custom CWM or TWRP (or both), start a companion forum on here and also a GitHub, so that we can open up our findings to Dev's who know what the hell they're doing :P

I have a feeling we're extremely close to having this work, but we'll just have to wait and see. I'm working on the CWM build in Linux right now, but it's going slow, because I'm at work for the next 8 or so hours, and I'm stuck using a VM. That having been said, I should have a preliminary build ready by tomorrow, but I need some way to test it without ACTUALLY flashing it to my phone (it's the only one I have and I can't afford to have it go down for more than an hour). Any ideas?

There's something we have to submit to the app dev to get a patch for full support. I'm assuming it should just be the recovery.fstab that shows all of our specific mount points and file-system types. I sent an e-mail on this to the app dev, and I'm just waiting to hear back. I'll post the results once I get them!
[Android General] Junkie2100:
specific mount points are irrelevant for the most part. they use a by name system now. if anyone knows hoe to build cwm or wants to get me a config.gz from their phone ill see what i can do, should be identical to the warp lte n9510 which i just finished making an initial cwm for. also the devices codename wouldnt hurt to have, its in the buildprop

if you want to do it head over to my github

github.com/junkie2100

and tweak the warp3 repo. ums doesnt work tho and internal sd isnt enabled

---------- Post added at 01:22 PM ---------- Previous post was at 01:10 PM ----------

also...

adb reboot bootloader

fastboot boot recovery.img

wont install cwm, it will just boot it, next recovery boot it wont be there ;)
[Android General] DaemeonZane:
Of course it won't; you just told it to boot the recovery; you have to actually use fastboot to flash the recovery image :P The device's codename is HERA, as observed in the build.prop for the device.

I'm working on the build for CWM using the methods I've found here on XDA, but you're more than welcome to download the packages I uploaded. The two image files were obtained using the good old dd command, and the system.ext4.tar was using a Nandroid Online backup app. It was good enough, apparently, for the dsixda kitchen to work with, though I haven't fully tested the ROM I have ginned up. All I did was zipalign, add init.d support, add SU & SuperSu, and intergrated busybox, though I'm working on making other stuff happen as well.
[Android General] Krsmqn:
[MENTION=2419585]Junkie2100[/MENTION] would this help?

https://www.dropbox.com/s/l2ayo4insgwnptb/system.info.gz
[Android General] DaemeonZane:
Spoiler content hidden.
[Android General] Junkie2100:
k codename hera. ill need the config.gz and i should be able to build it with no problem. its identical to the device i just got cwm working on last night

/proc/config.gz is the files exact location
[Android General] Krsmqn:
[MENTION=2419585]Junkie2100[/MENTION]

https://www.dropbox.com/s/82et8u1fmv5pv1w/config.gz

Here ya go. Just curious, but did you say that the recovery you built for the other phone wasn't working yet? If so, is there anything we could do to help?
[Android General] Junkie2100:
well, if you guys wanna take a look at my github, figure out whats goind on, why it soft bricks when you recover would be nice lol. it can be restored through advanced restore one partition at a time tho... im confused lol. but ill figure that one out

baaically all i ask is that you be patient till i get this fixed, once the warp 4g is done i basically plug this config.gz in, copy my warp3 stuff, change a few names, and build, i appreciate the offer tho. and btw im having a section created for this phone on androidforums.com

---------- Post added at 05:03 AM ---------- Previous post was at 04:48 AM ----------

i may need the folder name. it throws an md5 error eithout the right folder if im not mistaken
[Android General] Krsmqn:
Which folder?
[Android General] Junkie2100:
lol sorry i accidentally posted that on the wrong thread. disregard it

---------- Post added at 05:58 AM ---------- Previous post was at 05:53 AM ----------

got everything i need, just gotta solve the restore issue with the warp 4g and ill make you guys one too
[Android General] strykerhandy:
Hey guys.... Darn I don't check in for 24 hours and you guys have almost broke this coding haha... OK so I will just wait but I do have a lot of questions regarding the use of adb and fast booting and actually I need to learn everything about this device. It is very different from my old HTC and there was tons or Dec pre-written programs so to watch this u fold is awesome... So if you guys have to to school a noon here are some questions I know yo guys can answer...

How do we use adb with HERA

how do we get to the stock recovery

How do I get sdk

How do I use sdk and is it even something I should be talking about yet?

What commands do I need to now to use adb for ask transfers and last but not least has anyone got the root to keep? I have done everything I know how to do and it seems to stick now but I have had to root my phone 3 times and I barely read about making superuser a system app but will it stick now?

Thank you guys again

---------- Post added at 11:26 AM ---------- Previous post was at 11:16 AM ----------

Hey man hows it gking? I would love to try the method posted here but have nk clue where to start... could you give me some direction? Thanm you

---------- Post added at 11:42 AM ---------- Previous post was at 11:26 AM ----------

Hows the build going?
[Android General] Junkie2100:
well, adb on every device is basically the same. im on a phone so im not gonna go through every question but building hasnt started yet if you were asking me, i could make one that boots and then soft bricks your device every time you restore a backup, that will come in handy lmao. im working out the bugs in the warp 4g then it will be transferrable
[Android General] Junkie2100:
fixed said issue, seems to be working now. internal sd doesnt get mounted, usb mounting doesnt work, not sure of any other bugs. building you guys a cwm now
[Android General] Junkie2100:
http://unleashedprepaids.com/upload/devs/junkie2100/hera_cwm.img

that is the cwm, test it out let me know how it works. and there should be a forum section dedicated to your device on androidforums.com in the next day or so so keep an eye out for that. i put in a request but it takes time
[Android General] Krsmqn:
Thanks! I'll test when I get home.
[Android General] Junkie2100:
good stuff. also i may need to mention that you will probably have to use the "terminal method" of installation. root is required, then you will have to put it on the root of your sd card, and use a command similar to this

dd if=/sdcard/hera_cwm.img of=/dev/block/mmcblk0p##

substituting ## for the partition number of recovery, warp 4g is 16 but i cant say yours is for certain

of=/dev/block/platform/mmc_sdcc.1/by-name/recovery

may also be an option but i cant say for sure it didnt work the first time i tried that on the warp but its a different phone and it was half bricked at the time

fastboot doesnt seem to work on newer ztes for flashing, so i suggest this route, can be done through terminal emulator on the phone or using a computer with an adb connection via adb shell

also keep in mind you have to do

su

before the command or it wont have permission

---------- Post added at 05:36 PM ---------- Previous post was at 05:11 PM ----------

side note, im also gonna see if i can swing getting you guys a custom kernel. oc to 1.7ghz, various other enhancements. cant make any promises kuz thats not my department but the zte awe has one that should be transferrable
[Android General] Krsmqn:
Is there something I must do with those lines of code? I thought it was gonna be a flashable zip. I'm not savoy enough to know what to do with this. Great work though! I love the idea of an OC kernel!
[Android General] Junkie2100:
ah thats just it not downloading properly, its the encoded contents of the file represented as text. try using chrome instead it should then download

also it wont be as simple as a flashable zip, you cant flash a non zte zip in stock recovery sadly so youll have to run the terminal commands i stated

su

dd if=/location/of.img of=/recovery/partition

copying and pasting that wont do anything, you have to adjust obviously but that is the dd commands format and explaination

the sd is /sdcard/

a folder called folder on the sd is /sdcard/folder/

so if you put the file in the folder folder on the sd and named it recovery.img instead of hera_cwm.img the if= part changes to

if=/sdcard/folder/recovery.img

of stands for output file

if stands for input file

the partition thing you guys will have to work out sadly i dont know your partition layout
[Android General] Krsmqn:
I think we figured out that it's mmcblk0p16. Thanks a bunch. I will try the new link soon.

-------------------

Download successful from chrome.
[Android General] Junkie2100:
k good stuff, so of=/dev/block/mmcblk0p16

just be careful, if you flash the wrong partition you could brick, and you are the guinea pig lol, so this recovery may do more harm than good. chances are itll work fine, but theres always the possibility of failure
[Android General] strykerhandy:
Ok i also got it to download and i want to do this but as for as knowledge on what to do step by step i am dead in the water..... its in my downoad file and i think what you are sayijng is to put it in mu root file then go to terminal and give commands to install. Could eother of you make the full command out for me.to copy and paste or if you have the time/patience woukd you teach me what i

am doing?
[Android General] Junkie2100:
ok, root of the sd is where you put it. that just means out it on the sd card, not in a folder just straight on the card

if youre doing it through terminal emulator on the phone just fire it up, if you want to do adb through a computer you will have to get adb and do

adb shell

not gonna go through all the steps for getting adb and installing the drivers so youll have to look them up

the commands will then be

su

dd if=/sdcard/hera_cwm.img of=/dev/block/mmcblk0p16

granted thats the correct partition
[Android General] DaemeonZane:
Damn, I have seriously gotta set up a subscription to this post :P I go to sleep and wake up to a CWM recovery :P Our partition table is as follows:

mmcblk0p8 = /persist

mmcblk0p14 = /firmware

mmcblk0p15 = /boot

mmcblk0p16 = /recovery

mmcblk0p18 = /system

mmcblk0p21 = /cache

mmcblk0p22 = /data

These are the most pertinent partitions, and don't reflect the entire partition table. Download Partition Table to verify. If this CWM build is verified as ready for trials, I'll give it a shot.... but I have toask a serious question. The recovery.img that I created.... if this CWM build isn't stable, you think I'd be able to wipe it using the fastboot flash of the stock image?
[Android General] Krsmqn:
Subscribed!

(But of course... I made the thread..)

Hey XDA ... can we have our own forum now? ... :)
[Android General] strykerhandy:
Ok can i use the terminal on ROMtoolbox pro?
[Android General] Krsmqn:
Yes.
[Android General] strykerhandy:
Sweet it worked but its doinf something odd. When i scroll it shifts over with every other click so it looks as if it was moving back and forth on the screen. Also i cant get my reception bars to turn blue at all anymore. I restored my titanium back zip throigh cmwr and it didnt fix it. Before i tried the back up restore i got an error notification that said

"UNFORTUNATLY COM.ANDROID.PHONE HAS STOPPED WORKING"

I then rebooted and restored the zip.... anyideas or advice on either problems?
[Android General] Krsmqn:
So your phone has stopped working? There's a way that you can restore the old recovery image. I think that you could just use the recovery image that came stock and use the same code to install it.
[Android General] Junkie2100:
im confused as to what exactly thr problem is... did the signal bars mess up after installing cwm but before running a restory or flashing something using it? also there are no flashable zips for it so if you did install something it was probably the issue
[Android General] DaemeonZane:
Are you able to make calls at all? If no, then likely something else has happened, like some data being pushed to the partition holding the radio or something. Do yourself a favor and use Rom Toolbox pro or something to first fix permissions, then reboot, see what happens... If it doesn't help, you can try using Titanium Backup or some such to restore the system .tar that I uploaded.... I'm working on a good META-INF folder and scripting so that the image can be CWM-flashed, but it'll do no good if the CWM we have isn't working....

As for the screen bits... that's weird as ****, and I haven't got a clue
[Android General] Krsmqn:
Success!!!!

Ok... So after installing I now understand what he meant... and I took pictures. First of all, I didn't have any problems with my UI or and thing else. The only issue is the screen skipping around, which you can see in the attached pics.

I did a backup. 1st!!!!

Successful too!

So......

Who is going to provide a rom? Now that we can test them. :D

BIG THANKS TO Junkie2100 and DaemeonZane for their hard work!!! And strykerhandy for being the brave one to test it first!
[Android General] Junkie2100:
thats more than a little odd... but it works even if its a little ugly lol. i screwed up my cm10.1 repo so it may be a bit before i can make any adjustments. ill upload the tree to my github soon tho in case someone else wants to tinker
[Android General] Krsmqn:
Yeah , if you can get past the glitches, then it seems to work perfectly. But I haven't fully tested all the options for lack of reasons. Still, thanks man. The door is wide open for this device now!
[Android General] strykerhandy:
Thanks a million and i wish i could see how you did it.... i am stoked aboutt.it for sure. Hey i did have a UI problem... i though i just messed up with the backup zip though... the ui stopped working but i have ADW EX installed so it just stopped loading the settings and the menu bars, thats in additjkn to the connectivity problem.... i gor everything bck up and running though via titanium and wiping all data not just user. I think the problem woth the recovery glitch has to do with the gpu?
[Android General] DaemeonZane:
Based on what I'm seeing here, I half wonder if it may not be an issue with LCD Density or something along those lines. I'm gonna download it and see what I get. The main thing is this, and it's for Krsmqn or strykerhandy: Have either of you deleted any of the bloatware, or did you just use TB to freeze it? If you're still working with the bloat, do the N9511 community a favor and do a CWM backup of your phone, and upload it here for the OP. This way we can encourage developers do download and work with the image, as well as have something to restore to stock from should something go wrong. I myself have deleted ALL of the bloatware, and a few things that may have been important, but I haven't seen any undue issues, so it is what it is.

I'm going to get in contact with some buddies of mine on AndroidForums to see about getting some Dev's on this. The ROM I tried to build with the DSIXDA kitchen blew balls; it didn't even TRY to flash properly. Still, I'm not going to give up, no matter what. Stay tuned, Source Fans!
[Android General] Junkie2100:
heres the messed up thing, it should be identical to the warp 4gs cwm and the two devices are nearly identical, but the warp doesnt do that... no clue why one would and the other wouldnt

---------- Post added at 01:25 PM ---------- Previous post was at 01:22 PM ----------

on a good note tho, the zte awe and warp 4g being so similar means that the roms should basically be interchangable with a tiny bit of tweaking for the carrier differences. one collective dev team can cover all 3 devices
[Android General] DaemeonZane:
It happens, man. I'm gonna try to take a look at it and compare it to what I've got on my manual attempt and see what's different. I'm gonna do my best to make this happen.... I just need recommendations for a decent kitchen for cooking up a sweet little rom
[Android General] Junkie2100:
i dont use kitchen... so i couldnt tell you. manual hacking on occasion, mostly source building like cm. but hey heres the brand new section on androidforums

http://androidforums.com/zte-source/
[Android General] Krsmqn:
I will upload the stock backup this weekend. . . Unless someone else beats me to it.
[Android General] strykerhandy:
Kitchen is the term for??? And can any one tell me how to reinstall stock apps? I must have deleted my stock browser and keyboard yesterday while i was trying to fix some stuff... oh hey i had a major UI malfunction where it said my ui had stopped and then i troed to tap the menu or start button and it would say that the application was not installed.... have no clue whhy but i restored my backupzip via cwm and it still didnt fix it. So i factory restored my device and reinstalled the zip again and it worked but then my patches were not attatched to the right apps any more.... i figured i loaded something wrong but now that i am reading the posts from last night maybe not? I am not sure what i can do about the lack of internall memory but if you guys have dome something to up it or have a suggestion let me know please.. the stock as are.priority for me right now.though so please if you have advice on both let me know.about the aps first... thanmk you guys
[Android General] Krsmqn:
I will upload a stock recovery this weekend... if you can wait till then. You will be able to place it on your sdcard and then use cwm to restore ... it will have root as well.
[Android General] strykerhandy:
I can wait its worth it.... is there a way that i can delete everything on the device and reinstall? I mean all system and user and anything that dkesnt come stock?
[Android General] Krsmqn:
System apps are all stock except for superuser. User apps will be few if any.
[Android General] Krsmqn:
****Updated OP with Stock Rom w/root****
[Android General] Junkie2100:
kitchen is a program, normally referring to dsixda kitchen though there are others some more risky than others. it helps you unpack and repack roms, kernels, and recoveries. i do use it for boot.imgs and recovery.imgs and for deodexing(removing the small odex files that contain part of apps loaded into memory on startup for quicker startup of the app but slower startup of the rom) but if i dont often cook(the process of taking an existing rom and tweaking it to make something new) roms, i build them from source 9 times out of 10 and what isnt source built is just a custom variation on stock designed for my specific needs directly on the phone on piece at a time, nothing really release worthy
[Android General] Krsmqn:
Did you add the device "hera" to the kitchen as per the instructions?
[Android General] strykerhandy:
ok i did it!!! i bricked my device.. help... i have no clue what to do
[Android General] Krsmqn:
How? What steps did you take?

Sent from my JellyBeer Fire HD
[Android General] strykerhandy:
i was playing around with the cwm menu and formatted my system then tried to installl a backup and some how it went wrong and there is no funtionality anymore at all. it can biit inti recovery but nothing past the zte screen...
[Android General] Krsmqn:
So you can get to recovery... good. Download the backup Rom I uploaded and place it on your sdcard (use a computer and micro sdcard adapter). if your sdcard needs to be formatted then do it. (Fat32) After you can access the sdcard, create a folder called clockworkmod. Open it and create a folder called backup. Place the backup Rom folder in the backup folder. Make sure you unzip the download before you place it in there. Then put your sdcard in the phone. Boot into cwm. You might have to go to mounts and mount the sdcard. After it's mounted, choose restore and choose the backup'd Rom. Reboot when restore is done.

Try that. Unless I read your post wrong..?

Sent from my JellyBeer Fire HD
[Android General] strykerhandy:
OK...i think you read it right. i dont have a card reader though and i can get int o the recovery mode but i dont know how to do this with out a card reader do you?

---------- Post added at 01:00 AM ---------- Previous post was at 12:50 AM ----------

hey the dropbox link is saying that there is noting at thaat link anymoe.. where can i get the stock rom from now? oh man and thatnki you a million
[Android General] Krsmqn:
My bad....