Database Develop

[Q] broken recovery on stock 4.2.2

Dear all,
I've a tf701 with stock 4.2.2 build JDQ39.WW_epad-10.14.1.2820130827
I've been able to root it through adb/fastboot.
I tried to use the same way to flash the recovery and adb says "ok"
Problem is that when I launch RCK on fastboot; it starts normaly, not in recovery.
I'd tried to update the tf701 but update process tried to restart in recovery and it is the same thing I describe above.
I tried also rom manager to flash the recovery but the device is not superted yet.
If somebody could help me providing a recovery.img that work with JDQ39.WW_epad-10.14.1.2820130827 it would be great
Thanks in advance for tips and comments

guerito73 said:
Dear all,
I've a tf701 with stock 4.2.2 build JDQ39.WW_epad-10.14.1.2820130827
I've been able to root it through adb/fastboot.
I tried to use the same way to flash the recovery and adb says "ok"
Problem is that when I launch RCK on fastboot; it starts normaly, not in recovery.
I'd tried to update the tf701 but update process tried to restart in recovery and it is the same thing I describe above.
I tried also rom manager to flash the recovery but the device is not superted yet.
If somebody could help me providing a recovery.img that work with JDQ39.WW_epad-10.14.1.2820130827 it would be great
Thanks in advance for tips and comments
Click to expand...
Click to collapse
DO NOT USE ROM MANAGER! Fastest way to brick a transformer. Lucky you didn't.
Which recovery are you trying to flash?
Have you tried upgrading to 4.3 from Asus?

sbdags said:
DO NOT USE ROM MANAGER! Fastest way to brick a transformer. Lucky you didn't.
Which recovery are you trying to flash?
Have you tried upgrading to 4.3 from Asus?
Click to expand...
Click to collapse
I tried to flash CWM recovery, on adb it was a file called recovery.img but to my understanding it works with the asus stock 4.3 not the 4.2.2
OTA asus update dosn't work
I tried to update placing a SD card with the asus update, got a notification that my device will be updated but.... nothing the device restart (guess try to boot on recovery so fails and start normaly
still stuck there

Any ideas?
Somebody known if it is possible to flash CROMI X from a PC thanks to adb for instance?

guerito73 said:
Any ideas?
Somebody known if it is possible to flash CROMI X from a PC thanks to adb for instance?
Click to expand...
Click to collapse
See the recovery for 4.2.2 here:
http://forum.xda-developers.com/showthread.php?t=2622594
then you can upgrade to 4.3 from below:
http://forum.xda-developers.com/showpost.php?p=49969993&postcount=21

Many thanks, I restored the CWM recovery
May I upgrade from stock 4.2.2 with CWM recovery to CROMI X stable?
Thanks again

guerito73 said:
Many thanks, I restored the CWM recovery
May I upgrade from stock 4.2.2 with CWM recovery to CROMI X stable?
Thanks again
Click to expand...
Click to collapse
No you must go to JB 4.3 10.26.1.18 first.

ok i've tried to install jb-4.3_ota-full_t701t_macallan.zip trought CWM recovery for 4.2.2
it failed
says assert failed getprop ("ro.product.device") == "tf701t" || getprop ("ro.build.product") "tf701t"
error in /emmc/10/jb-4.3-ota_full_tf701t_macallan.zip
any idea?

guerito73 said:
ok i've tried to install jb-4.3_ota-full_t701t_macallan.zip trought CWM recovery for 4.2.2
it failed
says assert failed getprop ("ro.product.device") == "tf701t" || getprop ("ro.build.product") "tf701t"
error in /emmc/10/jb-4.3-ota_full_tf701t_macallan.zip
any idea?
Click to expand...
Click to collapse
Easier if you install the stock 4.2.2 recovery from that url and then put the zip inside the asus firmware zip in the root of internal or micro sd and reboot. It should update to 4.2.2 that way. I don't think you can flash asus stock roms from CWM yet.

Ok,
I flashed the recovery found at this url: http://droidbasement.com/asus/tf701t/stock/
It won't start, I boot android normaly instead of the recovery I think it is a recovery only for 4.3
The only recovery I've found for 4.2.2 id CWM

guerito73 said:
Ok,
I flashed the recovery found at this url: http://droidbasement.com/asus/tf701t/stock/
It won't start, I boot android normaly instead of the recovery I think it is a recovery only for 4.3
The only recovery I've found for 4.2.2 id CWM
Click to expand...
Click to collapse
Some news; flashed several times the recovey, adb flash without errors but trying to update asus update (WW_10_26_1_18_SDupdate.zip or WW_epaduser_10_26_1_18_UpdateLauncher.zip) my tf701t restart and that's it, no do anything more and I still stuck to 4.2.2 JDQ39.WW_epad-10.14.1.28
I've contacted asus; I hope they will be able to help me to restore the recovery.

just to be sure, it is not possible to flash the stock firmware from adb console?

guerito73 said:
Some news; flashed several times the recovey, adb flash without errors but trying to update asus update (WW_10_26_1_18_SDupdate.zip or WW_epaduser_10_26_1_18_UpdateLauncher.zip) my tf701t restart and that's it, no do anything more and I still stuck to 4.2.2 JDQ39.WW_epad-10.14.1.28
I've contacted asus; I hope they will be able to help me to restore the recovery.
Click to expand...
Click to collapse
You have to unzip the ....UpdateLauncher.zip once which will give you a .....user.zip. That's the file you need to flash.

Yes I know, I've do that, it has detect a firmware and starts the update process but only restart the tab.
After that, when I plug again the SD card with user.zip nothing...
Firmware is no longer detected on SD card.
Still with recovery issue that's why I wonder if it is possible to flash stock ROM through adb.

guerito73 said:
Yes I know, I've do that, it has detect a firmware and starts the update process but only restart the tab.
After that, when I plug again the SD card with user.zip nothing...
Firmware is no longer detected on SD card.
Still with recovery issue that's why I wonder if it is possible to flash stock ROM through adb.
Click to expand...
Click to collapse
Not in ADB - Android can't be running when you flash the system partition but you can flash the system blob in fastboot.
Check this out: http://forum.xda-developers.com/showthread.php?t=2179759&page=2

berndblb said:
Not in ADB - Android can't be running when you flash the system partition but you can flash the system blob in fastboot.
Check this out: http://forum.xda-developers.com/showthread.php?t=2179759&page=2
Click to expand...
Click to collapse
Ok thanks for the info.
I no response from asus support concerning a way to restore the 4.2.2 recovery I'll do that.
Just to be sure, I erease ell partitions (system, recovery, user data, boot, misc, cache and only flashing system (blob file) will re write every partitions?

guerito73 said:
Ok thanks for the info.
I no response from asus support concerning a way to restore the 4.2.2 recovery I'll do that.
Just to be sure, I erease ell partitions (system, recovery, user data, boot, misc, cache and only flashing system (blob file) will re write every partitions?
Click to expand...
Click to collapse
.
The system blob contains everything: kernel, recovery and system files. It does not re-write user data naturally, and I don't think you have to wipe that partition. Doesn't sound as if your trouble is related to user data.... So you should erase system, boot and recovery. I would also erase misc and cache - can't hurt...
Here's a link with a very good step-by-step guide: http://forum.xda-developers.com/showthread.php?t=2195883

Ok, thank you for your interest.
I confirm that with recovery CWM for stock 4.2.2 it is not possible to flash the firmware provided by Droidbasement.
got the error message:
assert failed getprop ("ro.product.device") == "tf701t" || getprop ("ro.build.product") "tf701t"
error in /emmc/10/jb-4.3-ota_full_tf701t_macallan.zip
Click to expand...
Click to collapse
I tried to go back to stock recovery but the one provided on droidbasement doesn't work; when "RCK" selected on fastboot mode, it says "booting recovery kernel" and restart the tab; that's all.
Same thing when tried to update asus stock firmware placing the update on SD card it's only reboot the tab.
To my understanding the stock recovery image provided by droidbasement works only with 4.3 stock not 4.2.2 stock.
So I'm able to flash a recovery CWM for 4.2.2 but can do nothing with it and not able to go back to a workable stock recovery
When I try to flash the stock recovery on droidbasement, it just restart the tab, still stuck at this step since 1 week.
I'm waiting a response from asus support I asked them a recovery image for stock 4.2.2
If they are not able to help me, I'll considere to flash the blob in fastboot.
Obviously if someone get tips to help me I'll reconsidere my plans

guerito73 said:
Ok, thank you for your interest.
I confirm that with recovery CWM for stock 4.2.2 it is not possible to flash the firmware provided by Droidbasement.
got the error message:
I tried to go back to stock recovery but the one provided on droidbasement doesn't work; when "RCK" selected on fastboot mode, it says "booting recovery kernel" and restart the tab; that's all.
Same thing when tried to update asus stock firmware placing the update on SD card it's only reboot the tab.
To my understanding the stock recovery image provided by droidbasement works only with 4.3 stock not 4.2.2 stock.
So I'm able to flash a recovery CWM for 4.2.2 but can do nothing with it and not able to go back to a workable stock recovery
When I try to flash the stock recovery on droidbasement, it just restart the tab, still stuck at this step since 1 week.
I'm waiting a response from asus support I asked them a recovery image for stock 4.2.2
If they are not able to help me, I'll considere to flash the blob in fastboot.
Obviously if someone get tips to help me I'll reconsidere my plans
Click to expand...
Click to collapse
I think you are wasting your time waiting for a response from Asus. They do not provide support for our flashing shenanigans

berndblb said:
I think you are wasting your time waiting for a response from Asus. They do not provide support for our flashing shenanigans
Click to expand...
Click to collapse
Yes, you are right, asus support just tell me a kind of **** you...
As asus blob file get everything including the recovery, I've downloaded the 4.2.2 update from asus and unpack the blob to get the recovery.img
unpacking blob file I've got:
blob.BC1
blob.BCT
blob.EBT
blob.PT
Anybody knows where is the recovery file and how can I do to make it flashable?
EDIT: I guess recovery is not in the blob file but in a recovery folder containing recovery-from-boot.p

[Q] stuck in bootloop

i've unlocked my bootloader,rooted and installed twrp...i did all the required wipes and tried to install the titan rom 1.1.0..i thought the flashing has started but it came up with an error-"error executing updater binary in zip" i tried it the second time and the result was same..now when i tried to boot my phone up..it just hangs at the -"warning unlocked bootloader" screen..the phone isn't switching off and unable to enter the recovery...i can go to the fastboot mode..but when i select recovery..it doesn't go to twrp..it again gets stuck at the boot screen..what can i do now?

Flash stock image

Similar problem in another thread I just posted to. I am having similar problems.
If after flashing stock then flash custom recovery to be able to go into recovery ?

Hello, I need to know what version of firmware you were, I think, will have to increase the bootloader to install again and there TWRP, flash any ROM

ghostzz said:
i've unlocked my bootloader,rooted and installed twrp...i did all the required wipes and tried to install the titan rom 1.1.0..i thought the flashing has started but it came up with an error-"error executing updater binary in zip" i tried it the second time and the result was same..now when i tried to boot my phone up..it just hangs at the -"warning unlocked bootloader" screen..the phone isn't switching off and unable to enter the recovery...i can go to the fastboot mode..but when i select recovery..it doesn't go to twrp..it again gets stuck at the boot screen..what can i do now?
Click to expand...
Click to collapse
Make sure you're using TWRP 2.8.6
Do all your wipes, reboot again into recovery, go to mount and make sure system isn't checked, go to install and try to flash again.
Sent from my XT1064 using Tapatalk

Trying to get back to stock rom

Hello,
Tried rooting my phone with no prior experience. Worked, but eventually I got to where the phone wouldn't boot past splash screen (logo came up, then screen went black while backlight is on and didn't respond to stimuli until battery was removed). Possibly resulted from a build.prop file problem. Did get into boot though, so I fixed that problem by installing a cyanogen rom from a zip file using twrp recovery. I didn't want a custom mod though since I'm used to the look and feel of the 4.0.3 ICS I had, and the cyanogen doesn't seem to have google play so I can't even download anything (original purpose of rooting was to get incompatible apps by spoofing via build.prop file). Currently trying to get back to stock. Unfortunately I didn't make a nandroid backup of the system before the problem occurred, hence I have no backup to flash.
What I tried:
1. Use the official HTC 4.0.3 RUU .exe to upload to the phone. Unfortunately HTC Sync doesn't see this phone, even though I have the correct drivers installed.
2. Attempted to use twrp recovery to install the rom.zip extracted from the RUU directly, the same way I successfully installed the cyanogenmod rom. Failed, claiming it's unable to open zip. The .zip file was checked for integrity and returned by an archiver app.
3. Tried to use these commands from the cmd with phone connected to install the .zip from fastboot:
fastboot erase cache
fastboot oem rebootRuu
fastboot flash zip rom.zip (rom.zip being the functional file of the stock rom)
Failed, saying it's not allowed. Tried it with both locked and unlocked bootloader, no difference.
4. Unzipped the file and tried to flash the system.img file directly, but that failed with a "data length is too large" error.
5. My recovery being twrp 2.1.1, tried looking for altenatives. Can't find any links to download the WCX recovery, but I found several for newer twrp versions, including 2.3.1.0 and 2.6.3.0 which I tried downloading flashing. After flashing the phone got stuck at the cyanogenmod loading logo and wouldn't boot further, and the recovery itself didn't work, just showed the HTC splash, turned black, then booted again normally, getting stuck at the cyanogen logo. Same thing for the 2.6.3.0 version, so I reflashed the original 2.1.1, at which point I can get into recovery but the phone is still stuck at the cyanogenmod during normal boot. At this point I installed the original cyanogenmod .zip from recovery and now at least the phone boots up normally. Still need to get stock back somehow.
Out of ideas and exhausted from this. Any help would be appreciated. Perhaps anyone has a working stock 4.0.3 rom for the Vivid, nandroid backup, etc., or any other ideas. Thanks for reading.

Oh crap...
OK... First... Stock rom can be found in development... Most of the roms there are stock... Read the OP... It'll tell you...
Second... You should use TWRP 2.5.3.0 or something like that I forget...
Third... When you tried the ruu... Did you relock your bootloader...
Side note... Could you get your phone to show up with 'fastboot devices'

TWRP for the mini one 2

Hello,
I tried to install the NostromoPop 2.1.2 ROM. Using fastboot I installed TWRP 2.7.x. I could boot it, but I did not work. I realized I downloaded the wrong version, so I downloaded 2.8.7.0 It was flashed but with "volume up" and "power" it won't start. My stock recovery starts immediately.
Any advices???

fall-out said:
Hello,
I tried to install the NostromoPop 2.1.2 ROM. Using fastboot I installed TWRP 2.7.x. I could boot it, but I did not work. I realized I downloaded the wrong version, so I downloaded 2.8.7.0 It was flashed but with "volume up" and "power" it won't start. My stock recovery starts immediately.
Any advices???
Click to expand...
Click to collapse
if stock recovery comes up then the flash failed. make sure you read the text in cmd.
did you unlock bootloader?

I follwed the guide for the CM. Everything worked so far.
I recieved no error message after flashing.

I can boot into recovery with the adb console, but still not with the power und volume buttons. Strang...

Ok, just installed Android 5.1.1. Works great on the Mini 2. HTC? No more! My next mobile will be a google phone!

Stuck on Samsung logo bootscreen after flashing TWRP through Odin (N920CD)

I have SM-N920CD variant and on stock Android M 6.0.1, Region:THR CSC:N920COJV2BPBA
I tried to flash TWRP through Odin in order to root and flash SkyHigh kernel but got stuck on Samsung logo bootscreen after flashing, I re-flashed my stock firmware to revive my phone and got it back working. I tried two different versions of Odin "Odin3 v3.10.7 and Odin3_v3.10.6" but still same results, I also used different PCs and downloaded TWRP twice.
Am I doing anything wrong or it is just me?

Did you try booting back to recovery and cleaning cache and rebooting. Sounds a little too basic I know but it has worked for me often enough. Just a thought.
Sent from my SM-N920G using Tapatalk

MSAKK said:
I have SM-N920CD variant and on stock Android M 6.0.1, Region:THR CSC:N920COJV2BPBA
I tried to flash TWRP through Odin in order to root and flash SkyHigh kernel but got stuck on Samsung logo bootscreen after flashing, I re-flashed my stock firmware to revive my phone and got it back working. I tried two different versions of Odin "Odin3 v3.10.7 and Odin3_v3.10.6" but still same results, I also used different PCs and downloaded TWRP twice.
Am I doing anything wrong or it is just me?
Click to expand...
Click to collapse
Try flashing again - this time ensure keep system as "read-only" option when you first flash TWRP. Then in TWRP recovery mode (straight after flashing & before rebooting), ensure that "system" is ticked/selected in the "Mount" option in TWRP menu - now reboot to system (you will need to tick/select "system" in Mount option each time if you boot into TWRP recovery mode).

swarup.siddharth said:
Did you try booting back to recovery and cleaning cache and rebooting. Sounds a little too basic I know but it has worked for me often enough. Just a thought.
Sent from my SM-N920G using Tapatalk
Click to expand...
Click to collapse
I can't even get to recovery, I can either get to download mode or stuck on bootscreen. I think it is the recovery getting messed up.

elmor0 said:
Try flashing again - this time ensure keep system as "read-only" option when you first flash TWRP. Then in TWRP recovery mode (straight after flashing & before rebooting), ensure that "system" is ticked/selected in the "Mount" option in TWRP menu - now reboot to system (you will need to tick/select "system" in Mount option each time if you boot into TWRP recovery mode).
Click to expand...
Click to collapse
I tried to enter recovery before rebooting and after flashing but with no luck. I assume to use the typical method (power+up+home). Am I missing something?

MSAKK said:
I tried to enter recovery before rebooting and after flashing but with no luck. I assume to use the typical method (power+up+home). Am I missing something?
Click to expand...
Click to collapse
Start all over again by re-flashing back to stock ROM/stock recovery and try again via Odin to flash TWRP - Make sure to go into recovery (TWRP) mode away straight away by 'power+vol up+home' buttons rather than booting into system.
Then mount system on in TWRP before rebooting to system - This worked for me, no probs since.
Also, ensure you have the correct TWRP .tar for your model (and ??maybe try an older Odin version for flashing TWRP).

Flash this TWRP through Odin:
https://dl.twrp.me/noblelte/twrp-3.0.0-0-nobleltezt-nobleltezt.img.tar.html

elmor0 said:
Start all over again by re-flashing back to stock ROM/stock recovery and try again via Odin to flash TWRP - Make sure to go into recovery (TWRP) mode away straight away by 'power+vol up+home' buttons rather than booting into system.
Then mount system on in TWRP before rebooting to system - This worked for me, no probs since.
Also, ensure you have the correct TWRP .tar for your model (and ??maybe try an older Odin version for flashing TWRP).
Click to expand...
Click to collapse
I tried that but nothing happened, it kept me on download mode otherwise system is booting.
Is it possible to enter recovery directly from download mode without power off?
Battlehero said:
Flash this TWRP through Odin:
https://dl.twrp.me/noblelte/twrp-3.0.0-0-nobleltezt-nobleltezt.img.tar.html
Click to expand...
Click to collapse
That is the download link I have been using.
Sent from my SM-N920C using XDA Free mobile app

I don't think you can go from download mode directly to TWRP recovery mode without power off.......... Try re-booting from download mode but before it re-starts quickly hold 'power+vol up+home'.
Have you tried starting from scratch i.e back to stock recovery, and tried flashing with an older version of Odin?

elmor0 said:
I don't think you can go from download mode directly to TWRP recovery mode without power off.......... Try re-booting from download mode but before it re-starts quickly hold 'power+vol up+home'.
Have you tried starting from scratch i.e back to stock recovery, and tried flashing with an older version of Odin?
Click to expand...
Click to collapse
I tried from scratch but with same results. Could it be ROM related?

elmor0 said:
Start all over again by re-flashing back to stock ROM/stock recovery and try again via Odin to flash TWRP - Make sure to go into recovery (TWRP) mode away straight away by 'power+vol up+home' buttons rather than booting into system.
Then mount system on in TWRP before rebooting to system - This worked for me, no probs since.
Also, ensure you have the correct TWRP .tar for your model (and ??maybe try an older Odin version for flashing TWRP).
Click to expand...
Click to collapse
i have tried that, and got an issues related to mount the storage as well, but able to overcome all that
and now the phone went from stuck on "Samsung" logo, into a loopboot
all this with the Samsung Stock ROM
but at the moment i install Lineage ROM, it works immediately
tried my best to make it work with samsung stock rom, but i couldn't