Database Info

No Recovery, garbled screen, can I recover?

I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks

Did you wipe before restore?

davebugyi said:
Did you wipe before restore?
Click to expand...
Click to collapse
Yes, I did a full wipe including dalvik cache before all restores. At this point, though, my primary concern is just finding a path back to usability!

DIncLover said:
I rooted my TF101 model B80 using RazorClaw (nvflash is a no-go for this model). Installed CWM, all was well. I tried to install Prime ROM from CWM, and was unimpressed; tried to restore my Nandroid backup of original rooted OS. Now, Transformer will not boot into any recovery (neither CWM or original green android), and screen comes up garbled. Is there any way I can restore my original stock by merely putting a particular image on my external sd card?
Any other suggestions welcome, I just can't get to a screen (recovery or otherwise) where there is any readable text I can respond to. Nor can I turn the device off. It will continue to reboot in this fashion. When I get home today I'll be able to start from a dead battery.
Thanks
Click to expand...
Click to collapse
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..

bruuuno said:
I had the same situation..I used the unbrick method:
http://forum.xda-developers.com/showthread.php?t=1123429
then you could try restore a backup ..
To turn off the device press the power button for 10-15 seconds..
Click to expand...
Click to collapse
I can try this when I get home today.... I'm just concerned because the method involves nvflash .... which I thought didn't work from the newer TF models (I have a model B80). I needed to wait for the RazorClaw exploit because previous attempts at using nvflash failed....

Then NVFlash will fail still...

davebugyi said:
Then NVFlash will fail still...
Click to expand...
Click to collapse
So am I hopelessly hosed?

Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.

baseballfanz said:
Sounds like this problem
http://forum.xda-developers.com/showthread.php?t=1321207&highlight=green+screen
Being you can't get back into CWM not sure how you'll flash the stock kernel.
HAve you tried Holding Vol Down button plus Power button till you get prompt to enter recovery at which time immediately push Vol up button withion 5 sec.
Click to expand...
Click to collapse
OK .... my bad.... I guess I wasn't pressing the buttons in the right sequence/duration. I CAN get to CWM!
So, once again, I try to restore the Nandroid backup and after rebooting, end up with the screen situation as in the reference you provided.
So, I am assuming my Nandroid backup is not restoring the kernel that it needs. I was running a recent OTA update; I believe the version was 8.6.5.19.
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?

DIncLover said:
Where can I get the appropriate kernel to install from CWM? Does it matter in what order I install the kernel and the Nandroid backup?
Click to expand...
Click to collapse
Look here
http://www.gnufabio.com/revolver/dls/

Same issue, no recovery though
Hi,
I have the same issue as the original poster, B80 serial, RazorClaw root. However, when I boot to recovery I get the green android with yellow triangle and exclamation mark.
I need to restore a recovery on my device as I may need to unroot to send to Asus. I have an even deeper problem of having to have the device connected to power for it to turn on after shut down.
However my main question is for that serial number and root method, what is the best way to flash a recovery on my device (stock or CWM) if I can not get into recovery to begin with?
P.S. RecoveryInstaller will not work, after installing the apk, I click the flash recovery button, the system holds for a bit, then nothing happens.
I will continue to search the forms for some answers, any insights or direction will be appreciated.
I can get into apx mode.
Thank you community!

I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?

gee one said:
I think you can flash the recovery via the staging partition. Search around the TF section, it's in here somewhere. Although, I wonder why the 1 click recovery didn't work?
Click to expand...
Click to collapse
Everything I see in the forms requires one of several conditions which my TF doesn't currently meet.
1. Recovery. I can not go into any recovery, thus I can not perform any flashing of any other rom or recovery.
2. B70 or later. Because of the security in the boot for these new serials, I can not use the NVFlash tools to un-brick / flash.
I am already rooted, however I do not know the reason for lack of recovery on this device. I unfortunately bought it yesterday from Craigslist, so not sure what this guy did before I got it.
I searched for flashing recovery staging partition and did not find anything immediately relevant. Please advice is there is a different wording I should use in my search as I am now getting an immense download on all of this trying to figure out what to do. I am also fairly new to Android devices having 1 other phone that is rooted.
Thank you for all the support and quick response! wonderful community here.

Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision

gee one said:
Try searching for posts with /dev/block/mmcblk0p4
This is particularly dangerous because you don't have access to nvflash. If you get bootloops, it is bricked. You have to be sure that whatever you flash will be 100% compatible with what you have now.
Also, when you try to boot into recovery, what does the text at the top say? There should be a version number in there somewhere.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Thank you gee one. I have since been able to install clockworkmod. My issue with the power not turning on if not plugged in still persists, I have started a separate thread.
I found your post on the staging partition here:
http://forum.xda-developers.com/showthread.php?t=1309949&highlight=power
Do you recommend this for the issue still persisting?
If so, considering I am on 8.6.5.19 will I have to use the blob from that? It is not on Asus website as I got it from the firmware update option in the settings before loading up my new ROM.
Do you recommend this step as the only resolution or is there another way?

Ok let me get this straight:
You have clockworkmod installed. Can you boot into it and do the buttons work?
Are you getting a garbled screen when you boot into the rom? Or are you just trying to unroot?
The tricky part is to avoid the bootloops of death.
sent from my cyanogen(mod) vision

Honestly what i would do if i were you, assuming i understood correctly that you can get into clockworkmod, just reflash the prime rom you didnt like(after wiping everything, including cache and dalvik), and if it boots and everythings okay, at least you know nothings really wrong with ur tablet. As for the plug in situation, make sure your battery isnt simply dead. As far as i know, it wont charge from recovery, so if uve been stuck without a booting rom for a while, it being dead could definitely be possible. Once you are in a working rom and you sorted out the charging issue, then you should worry about getting back to stock.

Thank you camaros,
I am able to load stock ROM successfully.
Battery is not dead as it is fully charged, and will run un tethered after powerup. I will test resetting it although I doubt that is causing it.
What i would like to determine is, is this related to a hardware or software issue?
Also, is there a way to restore stock recovery from CWM?

(Guide) System Restore Using TWRP

Update 1/2/18 : Removed link until we get a Restore that works across all device's.
This will will help you restore back to a clean OS install using Twrp.
1.Download Files to your computer Unzip and place "Stock Restore 123017" Folder in a folder Named "TWRP".
2.Move TWRP folder you created and place them on your Phone's SD Card or Push them using adb command
Code:
adb push TWRP /TWRP
3. While in Twrp recovery click Restore and navigate to the back up folder.
4. Restore all and reboot. First boot will take a couple of mins so give it time.
This should bring you back up from the dead.
Edit:
If you accidentally flashed Twrp in the wrong slot then only restore boot using this back up.
This should Fix any wifi issues you may be having.
https://mega.nz/#!ogclRKCL!YmOMbkhR8oc5MUdxUupdwxRe7BHJGUXRZnal5rW2S_w

Awesome, thanks again! Glad to see your ontop of things in the development of this phone!

@Xshooter726
Can this be used to rebrand the carrier version? Three are still slacking with the second update which I feel is affecting the camera and want to resolve it myself now dees has blessed us with recovery

I restored using your back up but the phone just stays booting for 10 mins plus and I have a warning with "Your device is corrupt"

PupPupG said:
I restored using your back up but the phone just stays booting for 10 mins plus and I have a warning with "Your device is corrupt"
Click to expand...
Click to collapse
What slot did you restore to? and is the message of corruption in TWRP?

PupPupG said:
I restored using your back up but the phone just stays booting for 10 mins plus and I have a warning with "Your device is corrupt"
Click to expand...
Click to collapse
Getting the same thing unfortunately. Might have to wait for the factory images.

CptClubs said:
@Xshooter726
Can this be used to rebrand the carrier version? Three are still slacking with the second update which I feel is affecting the camera and want to resolve it myself now dees has blessed us with recovery
Click to expand...
Click to collapse
Not sure. I don't have a carrier version to test it with.

fivearcosstheeye said:
Getting the same thing unfortunately. Might have to wait for the factory images.
Click to expand...
Click to collapse
Can you run Md5 check sum? I think my upload may have been interrupted.
MD5 Should match this
fe23d7ebb04818e5f3d661e5b67acee0

Xshooter726 said:
Can you run Md5 check sum? I think my upload may have been interrupted.
MD5 Should match this
fe23d7ebb04818e5f3d661e5b67acee0
Click to expand...
Click to collapse
Ran a check and the upload was correct. I've tried restoring the backup to both A & B but neither would work. I'm using a Three branded Razer Phone so it might just be something to do with that?

PupPupG said:
Ran a check and the upload was correct. I've tried restoring the backup to both A & B but neither would work. I'm using a Three branded Razer Phone so it might just be something to do with that?
Click to expand...
Click to collapse
Hmmm that maybe why. I was running the latest update when I did the back up and Three branded phones haven't received the latest update yet. Looks like Three branded phones will have to wait for Official Images. Sorry guys
..Well Unless someone with a clean os installed on a three branded phone does a back up similar to mine then that should work.

PupPupG said:
I restored using your back up but the phone just stays booting for 10 mins plus and I have a warning with "Your device is corrupt"
Click to expand...
Click to collapse
Xshooter726 said:
Hmmm that maybe why. I was running the latest update when I did the back up and Three branded phones haven't received the latest update yet. Looks like Three branded phones will have to wait for Official Images. Sorry guys
..Well Unless someone with a clean os installed on a three branded phone does a back up similar to mine then that should work.
Click to expand...
Click to collapse
I don't have a branded carrier version. Going to try a couple more things and if that don't work we'll have to wait for factory images or a custom rom.

When restoring using TWRP, we're supposed to include the 'Vendor' options as well as part of the restoring process? I also restored in both slots.
I have a feeling I just made a very expensive mistake when I tried restoring - left out the 'Vendor' (bottom two) and now it's been on the booting animation for a good 30mins. Can't force shut off by holding the power button or using the vol dwn + pwr to get into download mode. Holding vol up+pwr will get me the 'Razer powered by Android' splash screen and then it just goes back into the animation.

BakaSenpai said:
When restoring using TWRP, we're supposed to include the 'Vendor' options as well as part of the restoring process? I also restored in both slots.
I have a feeling I just made a very expensive mistake when I tried restoring - left out the 'Vendor' (bottom two) and now it's been on the booting animation for a good 30mins. Can't force shut off by holding the power button or using the vol dwn + pwr to get into download mode. Holding vol up+pwr will get me the 'Razer powered by Android' splash screen and then it just goes back into the animation.
Click to expand...
Click to collapse
Hey man, I ran into the same issue as you, so what I did was leave the usb plugged in and held down vol up+power till the phone's screen went black, then immediately held down the vol down button, this brought me into download mode, then I entered:
fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
into adb and my phone went back into twrp.
Can't help with the getting back into the system, I'm still waiting on that too, but hope this helps

Same for me. device corrupted after the restock restore on a US imported Razer Phone. Cant use it now. Have to get a replacement cheap phone since it is my daily phone lmfao.

My upload is for a full restore but if you have only messed up when flashing boot IMG and it's keeps going straight to Twrp then only restore boot from my back up. Your system should still be intact. I will upload just the boot.img alone.

If you accidentally flashed Twrp in the wrong slot then only restore boot using twrp.
https://mega.nz/#!ogclRKCL!YmOMbkhR8oc5MUdxUupdwxRe7BHJGUXRZnal5rW2S_w

Xshooter726 said:
If you accidentally flashed Twrp in the wrong slot then only flash this boot.img using fastboot to get you back to normal.
https://mega.nz/#!ogclRKCL!YmOMbkhR8oc5MUdxUupdwxRe7BHJGUXRZnal5rW2S_w
Click to expand...
Click to collapse
Maybe i am wrong but in this zip file is a twrp boot image not a boot.img file ?

Quashhh said:
Hey man, I ran into the same issue as you, so what I did was leave the usb plugged in and held down vol up+power till the phone's screen went black, then immediately held down the vol down button, this brought me into download mode, then I entered:
fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot
into adb and my phone went back into twrp.
Can't help with the getting back into the system, I'm still waiting on that too, but hope this helps
Click to expand...
Click to collapse
Hey, thanks for that suggestion! I was able to get into download mode and I flashed my phones own recovery and I got it to work. Wiped both a & b slot and restored both of them with my recovery.
The only problem (not so sure if it is an issue) is the backup I made is only of the Boot and System Image as per the TWRP instructions. So when I boot into slot a_ I get an error when I boot up 'There's an internal problem with your device. Contact your manufacturer for details.' Switching into slot b, I don't get that error. However, here's the weird thing (I think at least), when I go back into TWRP and switch to slot a, I get a bootloop into TWRP.: So, if I decide to continue on, and flash the TWRP zip file and then subsequently Magisk - I'll lose wifi and etc.
If I end up using Xshooter's full restore img - I'll do the same thing - wipe both slot a&b and restore both slots after. However, I'll get a message after the Razer splash screen say my phone is 'Corrupt' - and this is if I restore with the Vendor options. If I exclude the Vendor options, I'll be stuck in the animation. I lied - I'm stuck on the Corrupt screen now. I can get into TWRP at least...
So, in a bit of a bind here now.

BakaSenpai said:
Hey, thanks for that suggestion! I was able to get into download mode and I flashed my phones own recovery and I got it to work. Wiped both a & b slot and restored both of them with my recovery.
The only problem (not so sure if it is an issue) is the backup I made is only of the Boot and System Image as per the TWRP instructions. So when I boot into slot a_ I get an error when I boot up 'There's an internal problem with your device. Contact your manufacturer for details.' Switching into slot b, I don't get that error. However, here's the weird thing (I think at least), when I go back into TWRP and switch to slot a, I get a bootloop into TWRP.: So, if I decide to continue on, and flash the TWRP zip file and then subsequently Magisk - I'll lose wifi and etc.
If I end up using Xshooter's full restore img - I'll do the same thing - wipe both slot a&b and restore both slots after. However, I'll get a message after the Razer splash screen say my phone is 'Corrupt' - and this is if I restore with the Vendor options. If I exclude the Vendor options, I'll be stuck in the animation.
So, in a bit of a bind here now.
Click to expand...
Click to collapse
No problem, I was just about to give up and settle with a pretty cool paper weight till i tried that out, now i'm gonna try and restore the backup to both slots and try Xshooters method...
Fingers crossed

@BakaSenpai and @Quashhh if you both are able to put your backup on google drive to share it with me so that i can try some options? i have the same issue now. I hope you both get it sorted.
grtz
Steven

Phone currently stuck in fast boot screen, any help?

Hi guys,
I need a bit of help in regards to my oneplus 7 pro 5g edition (GM1920) I previously attempted to root the phone as always and have accidentally wiped the system via twrp, i am now currently stuck in fastboot mode and it appears that the phone has now wiped the factory recovery as every time i attempt to go into it via the fastboot screen or reflash twrp, it shows the 1+ logo for a split second and reboots to fastboot, usually with previous devices reflashing twrp would have been enough but it seems that there is nothing i can do at the moment, any help or advice would be much appreciated.
Thank you
SOLVED: Turns out it was rather simple, the phone wasn't flashing to the correct partition and wouldn't let me change, but randomly after a few tries it finally let me change to the correct partition and everything now works like a charm again.

Joshmc4 said:
Hi guys,
I need a bit of help in regards to my oneplus 7 pro 5g edition (GM1920) I previously attempted to root the phone as always and have accidentally wiped the system via twrp, i am now currently stuck in fastboot mode and it appears that the phone has now wiped the factory recovery as every time i attempt to go into it via the fastboot screen or reflash twrp, it shows the 1+ logo for a split second and reboots to fastboot, usually with previous devices reflashing twrp would have been enough but it seems that there is nothing i can do at the moment, any help or advice would be much appreciated.
Thank you
Click to expand...
Click to collapse
So if you are flashing TWRP through fastboot, it does the same and reboots to fastboot? Are you able to flash twrp successfully? If yes try power+volume down to go into twrp. Then change the slot

in fastboot use your vol buttons and scroll to RECOVERY and click power button after you flash TWRP

Hi guys,
Thank you for the suggestions but i manged to finally figure it out after hours of racking my brain, turns out it was a very simple solution, for some reason the phone was trying to flash to the wrong partition and wouldn't let me change partition, then randomly out of nowhere it did, so i was finally able to reinstall the stock rom and twrp and am now fully rooted with no issued at all.
Thanks again.

[HELP] Your device is corrupt. It can't be trusted and will not boot.

Today I rooted my OP7 Pro to recover my accidentally deleted file. But after recovery i try to come back to stock and remove root, I re lock me boot loader without coming to stock rom (I forget to remove TWRP recovery)
now i stuck on a black screen and can't do any thing no recovery, no edl, no boot loader nothing just phone in rebooting again and again
Pleas help me to fix it
Thanks in advance

https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Use this. It should fix it.

trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Use this. It should fix it.
Click to expand...
Click to collapse
that worked thanks :good::good::good::good::good:

My 7Pro shutdown and no matter what I do it will not startup/ turn on again. what would you guys recommend I try. Other then the obvious bottom combinations. Which do nothing.

Question samsung a536E stuck on bootloop

hello everyone, today i tried to flash twrp on my phone (rooted with magisk and running stock samsung rom), the flash was successful and i was able to boot into twrp but i coudnt access my storage or anything else, so i saw a guide saying to change the filesystem to ext2 then ext4, after i did that i could access most of the other folders but not the storage foldier as it still showed 0mb. i thought i just need to reboot my device to fix the issue but now im stuck on a bootloop. i cant poweroff the device since no button combination is currently working. is there anything i can do to power it off or do i have to wait a few days till the battery drains to 0?
[RECOVERY][UNOFFICIAL] TWRP for Galaxy A53 5G (Exynos)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
this is the link i used to flash twrp except i didnt follow the wipe instructions because i dont want to use a custom os.
and if nothing else works and i have to wait a few days till it drains to 0, will i be able to boot back into samsung's recovery mode or is this device hard bricked?
help will be greatly appreciated.

This phone doesn't have the nice feature of holding the power button for force off so that is a negative here.
I don't think you should have edit:changed the partition types. If that was necessary it would be a ridiculous thing for other Android roms to have to do. Its all Android so should have worked without that.
Its unlikely that anything new will result from a cold boot verses a warm boot. Worth a shot I suppose but don't hold your breath. Expect nothing new.
If its stuck without Odin, fastboot, ADB, all buttons not doing anything, can't ingest and do something from sd card, can't show up via USB on computer, etc with nothing at all then its totally finished since nothing can be done. Consider it a loss and learn from it.
I'd like to also state that there are for some reason people who supposedly bring roms over to devices and they don't have the device so therefore don't really know if it works or not. You have to be careful about the guides you follow. I've seen someone try with a device that could not be unlocked ever for anyone and that person thought it would work. Live and learn.

sandsofmyst said:
This phone doesn't have the nice feature of holding the power button for force off so that is a negative here.
I don't think you should have edit:changed the partition types. If that was necessary it would be a ridiculous thing for other Android roms to have to do. Its all Android so should have worked without that.
Its unlikely that anything new will result from a cold boot verses a warm boot. Worth a shot I suppose but don't hold your breath. Expect nothing new.
If its stuck without Odin, fastboot, ADB, all buttons not doing anything, can't ingest and do something from sd card, can't show up via USB on computer, etc with nothing at all then its totally finished since nothing can be done. Consider it a loss and learn from it.
I'd like to also state that there are for some reason people who supposedly bring roms over to devices and they don't have the device so therefore don't really know if it works or not. You have to be careful about the guides you follow. I've seen someone try with a device that could not be unlocked ever for anyone and that person thought it would work. Live and learn.
Click to expand...
Click to collapse
hello, i was able to boot the phone into twrp and do a factory reset, i had to time the vol up + power button at exactly the time when the screen went black and it worked!. but now i have a question, if i want to get twrp again and i dont plan to flash a custom rom like it says in the guide, how do i get twrp to recognize my storage? and do you flash twrp before installing an os or after because ive done it after installing the os.

floppen22 said:
hello, i was able to boot the phone into twrp and do a factory reset, i had to time the vol up + power button at exactly the time when the screen went black and it worked!. but now i have a question, if i want to get twrp again and i dont plan to flash a custom rom like it says in the guide, how do i get twrp to recognize my storage? and do you flash twrp before installing an os or after because ive done it after installing the os.
Click to expand...
Click to collapse
yeah so it seems like the issue isnt with changing the file system or anything because i installed twrp again and tried rebooting and i got the same bootloop issue, but if i flash a rom then ill lose twrp like it happened last time so i dont understand what im supposed to do

you have to format data in twrp otherwise it won't see your storage folder.
once formatted reboot to twrp then reboot to system, it should reboot to stock rom and the set up pages.

beanbean50 said:
you have to format data in twrp otherwise it won't see your storage folder.
once formatted reboot to twrp then reboot to system, it should reboot to stock rom and the set up pages.
Click to expand...
Click to collapse
wipe>format data>type yes>reboot to recovery. i did that and still cant reboot to system bootloop issue persists

yes you did it correctly this time, is there anyway to undo your 'filesystem to ext2 then ext4'?

or maybe you have to flash the custom kernel to get it all up and running again

beanbean50 said:
or maybe you have to flash the custom kernel to get it all up and running again
Click to expand...
Click to collapse
how do i do that? the kernel folder in the guide doesnt have any tar or .img file to flash

floppen22 said:
how do i do that? the kernel folder in the guide doesnt have any tar or .img file to flash
Click to expand...
Click to collapse
it's a zip file so it should flash in twrp

beanbean50 said:
it's a zip file so it should flash in twrp
Click to expand...
Click to collapse
yes i was able to boot into my phone after flashing the kernel. thank you so much.

Try a different version of TWRP I remember this happened to me before and I installed a different version and it was fine