Database Info

[Q] HELP!! TF101 not booting past CWM recovery

I was trying out this rom
http://www.theandroidsoul.com/cm9-cy...sformer-tf101/
and after flashing it, my table just kept restarting. So I decided to flash a different rom so I flashed this rom
http://forum.xda-developers.com/show....php?t=1520764
now this time, my tablet wouldn't boot past the CWM recovery. It just gave me a loading screen for hours.
After a couple hours of doing this over and over again, I decided to flash back to stock if it works. I was successful at this and was able to boot into stock. But since I'm too used to ICS on my tablet I decided to flash back my old rom which was
http://forum.xda-developers.com/show....php?t=1518768
for weeks I have been using it at home and at university, I had no problems with it, It worked really well for me.
But now it's doing the same thing, it's not booting past the recovery, It would only boot up until the Eee Pad welcome screen.
HELP!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

How did you flash back to your old rom? Zip or restore from a backup?
What version of cwm?
Also, your links are busted--- the xda links are missing "thread."

gee one said:
How did you flash back to your old rom? Zip or restore from a backup?
What version of cwm?
Also, your links are busted--- the xda links are missing "thread."
Click to expand...
Click to collapse
I tried to go back to my old rom using CWM but it just wouldn't work so I used nvflash to flash back to stock rom.
I used 3.0.1
http://forum.xda-developers.com/showthread.php?t=1525148 - CM9 with cornerstone (the rom I tried to use which caused all this)
http://forum.xda-developers.com/showthread.php?t=1520764 - Team eos nightlies (just wouldn't work after I tried CM9 with cornerstone)
http://forum.xda-developers.com/showthread.php?t=1518768 - Revolver 1.3.1 (My original rom)

If you have access to nvflash, then that would probably be the most expedient way to get to a working rom. It will probably wipe all your data. That being said, there are certainly more subtle ways to use nvflash. You could back up your data before wiping it clean, and then restore it afterwards. I think there is a thread in the dev section about using nvflash to backup your tf.

gee one said:
If you have access to nvflash, then that would probably be the most expedient way to get to a working rom. It will probably wipe all your data. That being said, there are certainly more subtle ways to use nvflash. You could back up your data before wiping it clean, and then restore it afterwards. I think there is a thread in the dev section about using nvflash to backup your tf.
Click to expand...
Click to collapse
Cheers for that! I used NVflash and flashed ICS. All worked well. Just wondering, can Revolver 4.0.0 beta 1.3.1 be flashed using NVflash?

You can flash anything you want with nvflash if you know the boot key and can repackage it.
sent from my android tablet

[Q] Error Wifi,. after Kernel failure

hi guys
ok, so I have a Sensation XE. I had the stock ROM, then added Fast Boot.
I wanted USB OTG support, so tried to [KERNEL] Overclocked kernel v1.5.2, not sure why, but it failed.
after that my phone was buggy. slow and the Wifi unhappy.
I thought ill just put a new kernel in, I ran [Aroma] Sultan kernel [r21 3/2/2013]
a bit better but not great.
I figured Ill start from scratch then:
So I flashed Darkforest Sensation XE 7.3.0 with Kernal:XxXPachaXxX_Custom_Kernel_stable3.1. this includes a COMPLETE wipe of the system using Aroma.
I thought this would fix the issue...
it didn't... the ROM is nice n slick, but Wifi - Error on the quick setting screen. cant be turned on.
whats gone wrong, and can I fix it?
I've tried http://forum.xda-developers.com/showthread.php?t=1456700 delete the "wifi_supplicant.conf" file.
Wold flashing a different Kernel fix this like http://forum.xda-developers.com/showthread.php?t=1230687 did.
if so, which Kernel, as with my noobness I'm not sure which ones would work or are fully compatible
Cheers for your help

Try ARHD. Then flash Sultan's r15. If problem still persists, use R15 with the BCMXXXXX thingy. It worked for me.

KiD3991 said:
Try ARHD. Then flash Sultan's r15. If problem still persists, use R15 with the BCMXXXXX thingy. It worked for me.
Click to expand...
Click to collapse
I've just tried the Sultan-kernel-r14-Aroma-BCM4329.zip, still the same wifi error.
I've also noticed that in Advanced Wifi, MAC Address: unavailable, IP Address: Unavailable

i was going through my boot loader. and when it checks itself it has image errors
see image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://www.dropbox.com/s/vkhw9s0qamionws/BootImageIssues.jpg

grymcent said:
i was going through my boot loader. and when it checks itself it has image errors
see image
https://www.dropbox.com/s/vkhw9s0qamionws/BootImageIssues.jpg
Click to expand...
Click to collapse
don't care about that.it is nothing
when you boot into bootloader it reads every time the sdcard and searching for pg58img.zip or pg58diag.zip
ignore it
now about your wifi issue
i saw that you are S-ON
i suggest to have 4ext recovery for flashing kernels and roms
and before flashing any rom or kernel enable smartflash from recovery
now try this way
flash the boot.img of the rom manually.if don't know how see here
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1 step)
then check your wifi
also can you tell me what error did you have with overclocked kernel 1.5.2?

rzr86 said:
don't care about that.it is nothing
when you boot into bootloader it reads every time the sdcard and searching for pg58img.zip or pg58diag.zip
ignore it
now about your wifi issue
i saw that you are S-ON
i suggest to have 4ext recovery for flashing kernels and roms
and before flashing any rom or kernel enable smartflash from recovery
now try this way
flash the boot.img of the rom manually.if don't know how see here
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1 step)
then check your wifi
also can you tell me what error did you have with overclocked kernel 1.5.2?
Click to expand...
Click to collapse
Sorry, I cant recall the error from flashing the Kernel.
I have tried to flash Recover.img and add 4Ext, however it seems I have TWRP 2.3.x
i did also flash the Boot.img for the DarkForest ROM to see if that made a difference..
nope nothing
also was directed to the PG58IMG.zip to fix firmware, but that didnt seem work according to their instructions either.

grymcent said:
Sorry, I cant recall the error from flashing the Kernel.
I have tried to flash Recover.img and add 4Ext, however it seems I have TWRP 2.3.x
i did also flash the Boot.img for the DarkForest ROM to see if that made a difference..
nope nothing
also was directed to the PG58IMG.zip to fix firmware, but that didnt seem work according to their instructions either.
Click to expand...
Click to collapse
after much searching and trying a few other ROM, I found a comment about other ppl having issues with ROM. but fine with the Stock ROM.
I have just put the Stock rROM on, its connected to wifi straight away.
hope it lasts!

[Q] Tried to use CWM to make a nandroid backup on 4.3 ML1. Is there a way back?

I rooted using Saferoot. I wanted to backup the phone before trying safestrap. After searching around a bit, it looked like a nandroid backup would be the way to go. To find out how to do this I followed the 2 links below:
http://forum.xda-developers.com/wiki/NANDroid
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
I downloaded ROM manager and proceeded to let it find the "correct version of CWM for your phone". In the process it requested root access and tried to flash a custom recovery. Then I got the following message when I tried to boot into recovery mode:
SECURE FAIL: KERNEL
System software not authorized by Verizon Wireless ...
After posting the result on the thread below, I was quickly told that I shouldn't try custom recovery on an ML1 OTA phone. Of course now, I sure wish I'd researched a bit more before trying.
http://forum.xda-developers.com/showthread.php?t=2653030
I didn't want to derail that thread any further so I started this one.
Is there anything I can do to undo what I've done? I don't really want to unroot, but it sounds like that has nothing to do with it anyways.
Should I still be okay to use Safestrap?

mrjim.com said:
I rooted using Saferoot. I wanted to backup the phone before trying safestrap. After searching around a bit, it looked like a nandroid backup would be the way to go. To find out how to do this I followed the 2 links below:
http://forum.xda-developers.com/wiki/NANDroid
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
I downloaded ROM manager and proceeded to let it find the "correct version of CWM for your phone". In the process it requested root access and tried to flash a custom recovery. Then I got the following message when I tried to boot into recovery mode:
SECURE FAIL: KERNEL
System software not authorized by Verizon Wireless ...
After posting the result on the thread below, I was quickly told that I shouldn't try custom recovery on an ML1 OTA phone. Of course now, I sure wish I'd researched a bit more before trying.
http://forum.xda-developers.com/showthread.php?t=2653030
I didn't want to derail that thread any further so I started this one.
Is there anything I can do to undo what I've done? I don't really want to unroot, but it sounds like that has nothing to do with it anyways.
Should I still be okay to use Safestrap?
Click to expand...
Click to collapse
You should be able to boot into Download mode (hold volume down, power, and home button) then do this debrick method by ThePagel.

Awesome thanks!
I tried to run saferoot again I got the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm really not sure what to do with this.
Edit: I see my build is different now. It is now NC1.
Yeah, I DL'd the wrong "tar ball". Time to run the Odin fix again with the "official old 4.3 tar ball".

Just make sure you download ml1 Odin file. The nc1 is junk and Verizon tool is pushing nc1. I'm going delete the nc1 link and note the Verizon utility in the op first chance I get.

Safe strap is what you use to make the nandroid backup. You can't install any other recovery unless you unlock the Bootloader which isn't possible on 4.3 ml1 or nc1.. Install safe strap, make backup and have fun.
Sent from my SCH-I535 using Tapatalk

Can't boot into fresh custom rom anymore -> keeps booting recovery (TWRP)

I was running OdexLite V4.2 but I was having some issues. I thought this was caused because I flashed it over my Marshmallow rom. So I flashed the latest available S6 edge official firmware from sammobile (G925FXXU5EQI6_G925FPHN5EQI2_PHN) and after that I fully booted the phone and shut it down. Then through Odin I flashed TWRP (twrp-3.1.1-0-zerolte.img.tar) and tried to install OdexLite again. I tried V4.2, V4.1, V4.0 but all of them kept rebooting me back into recovery. No matter what I tried. I haven't tried another ROM yet, tried to download NOBLE NOUGAT S8 PORT 5.1 but I don't have an Telegram account. I can't seem to find a download link without having to use my phone number.
What can be the cause of my phone to keep rebooting into the recovery? I already used V4.2 (till this morning) and it always worked. I redownloaded the file (V4.2 and TWRP) but that didn't change anything. Then I flashed back to stock Marshmallow like before, fully booted the system, shut down and install TWRP again. And then tried to flash V4.2 (and after that V4.1 and V4.0) but still my phone keeps rebooting into recovery after finishing the ROM. I tried various options in the aroma installer (stock choices and the same choices I made the first time when it worked)
I did a full erase (erase everything) and then copy the files through TWRP to the phone and flash it. And erased everything and used an OTG stick with the files to flash. I tried factory reset, wipe cache, etc. after the phone reboots back into recovery after the installation.
What's going wrong?? Please help me I don't know what else to try...

No, only the ROM files

rifek4 said:
That's maybe why...
Click to expand...
Click to collapse
I also replied to you in the other topic, I didn't had to do it before and the install instruction don't mention to install root either. But today I found flashing root can be the solution (while it wasn't mentioned in the startpost)
But V4.2.3 fixes the recovery loop. I'm now going to try V4.1 and/or V4.0 with flashinh magisk afterwards to see if that solves the problem.
Links to the solution page (page 100)
https://forum.xda-developers.com/ga...lite-rom-920f-920i-925f-925i-t3550706/page100
But thanks anyhow, I didn't know that I had to flash that. I just followed the instructions to be sure I didn't skip anything important :good::good:

rifek4 said:
Because that isn't nothing new and every one user who flashing custom ROM's must know that every time after flash ROM we must flash ROOT
Click to expand...
Click to collapse
I have flashed a_lot_of_roms on many different phones and I almost never had to do this. The times I had to do this, it was always instructed in the install routine I had to. Never had a loop to recovery before. I guess it was luck? Especially because the exact same rom worked before without flashing root. But this was a first for me and I'm flashing roms since the MDA Compact
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But I'm happy I've learned this today, wished I learned this already yesterday :silly: missed my sleep this night
(Nederlandse Pool?)

rifek4 said:
Yes, same for me, I modding phone since 2006/7 year then we did mainly Sony Ericsson's and Nokia modding, later was more... If you Google my nick names "Leito07" with "Sony", "Nokia" word then you will see my first mods, sometimes there even are files from almost 10 years ago, look HERE: http://www.topsony.com/forum/showthread.php/18057-SquaSh-WBXML-Acoustic-by-Leito07
But on currently models like S6 with custom 7.0 FW for example we always must flash ROOT to patch boot image, otherwise phone will give us bootloop...
P.S.
Yep, you? Nederlandse Dutch misschien? :laugh:
Click to expand...
Click to collapse
Nice! Haha
P.S.
Nee geen probleem, enkel nieuwsgierig haha. Ik gewoon Hollandse Hollander. Geen Turkse, geen Poolse, gewoon lekker standaard :laugh:

rifek4 said:
Jaaaa... Zo standaard niks... Ik weet dat je alle racisten bent, maar we praten niet over het hier...
Click to expand...
Click to collapse
Haha uiteraard. Nee gewoon een brave Nederlander. Wel fan van Poolse vrouwen

rifek4 said:
Because that isn't nothing new and every one user who flashing custom ROM's must know that every time after flash ROM we must flash ROOT
Click to expand...
Click to collapse
That's false. You don't need to flash root, only roms that need that, like Noble.

Markos said:
I was running OdexLite V4.2 but I was having some issues. I thought this was caused because I flashed it over my Marshmallow rom. So I flashed the latest available S6 edge official firmware from sammobile (G925FXXU5EQI6_G925FPHN5EQI2_PHN) and after that I fully booted the phone and shut it down. Then through Odin I flashed TWRP (twrp-3.1.1-0-zerolte.img.tar) and tried to install OdexLite again. I tried V4.2, V4.1, V4.0 but all of them kept rebooting me back into recovery. No matter what I tried. I haven't tried another ROM yet, tried to download NOBLE NOUGAT S8 PORT 5.1 but I don't have an Telegram account. I can't seem to find a download link without having to use my phone number.
What can be the cause of my phone to keep rebooting into the recovery? I already used V4.2 (till this morning) and it always worked. I redownloaded the file (V4.2 and TWRP) but that didn't change anything. Then I flashed back to stock Marshmallow like before, fully booted the system, shut down and install TWRP again. And then tried to flash V4.2 (and after that V4.1 and V4.0) but still my phone keeps rebooting into recovery after finishing the ROM. I tried various options in the aroma installer (stock choices and the same choices I made the first time when it worked)
I did a full erase (erase everything) and then copy the files through TWRP to the phone and flash it. And erased everything and used an OTG stick with the files to flash. I tried factory reset, wipe cache, etc. after the phone reboots back into recovery after the installation.
What's going wrong?? Please help me I don't know what else to try...
Click to expand...
Click to collapse
Make sure the ROM your flashing is ROOTED, if not ROOT is yourself and try again.

Reflash Stock fails with mismattached carrier ID and failure to verify dmverity

Hi,
i tried to reflash stock on my Galaxy S8+ G955F after having issues with flasing the latest Renovate ICE Rom (Android 8) with Magisc, which did not install., I read in another thread that Magic can fail to install when having SuperSU before which I had in the beta of that ROM, and the solution would be to reflash Stock and unroot. This is WHY I did it.
I downloaded from sammobile and flashed with ODIN. In another thread I found out that the dmverity problem could be fixed with removing the cache.img out of the CSC; which i did try, but with no effect.
I am guessing that the carrier mismatch is the actual problem. I have a german phone and I selected germany on the sammobile so I am not sure how there can be a mismatch.
I also tried to reflash TWRP but it wont go into TWRP which I guess might be because of OEM lock reactivated through stock rom flashing.
Anyone knows how I could proceed from here?
Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I will do some research

For my country there is only the Android 7 stock rom available. The custom rom I flashed before was Android 8 so could this be a problem? I am not sure if it will make things worse if I flash one of the available Android 8 versions with "wrong" CSC.

unimatrix27 said:
For my country there is only the Android 7 stock rom available. The custom rom I flashed before was Android 8 so could this be a problem? I am not sure if it will make things worse if I flash one of the available Android 8 versions with "wrong" CSC.
Click to expand...
Click to collapse
im worried I bricked my phone. Is there a way to unlock the bootloader without being able to boot the phone? so that way i could maybe use TWRS again and try a custom rom? I cant use fastboot as I can only go into download mode or in the stock recovery. Is this even the right place to ask about a solution? Im totally desperate. Thanks!

Jessooca said:
Did you get your phone fixed yet? I had a couple people PM me over the past couple weeks with the same issue, both phones work fine now. PM me if you still need your phone fixed.
If not, good stuff, have a great weekend
-Jessica
Click to expand...
Click to collapse
I managed to boot the phone into stock a few minutes ago. I dont know how i did it. I applied "Factory Reset" and "Wipe Cache" a few times and then it did boot. I did then check that OEM unlock is enabled, whcih it still was. I then tried to flash TWRP again, ending up with the same problem, that TWRP would simply not start and trying to start it just gives me the constant Boot logo (the one you see first after turning the device on) and obviously with TWRP now on it, the stock would not boot any more, so I reflashed stock, and now back to square 1. Factory Reset and Wipe cache have not worked so far.

Update:
I am able to get stock rom to work. No matter which version of ODIN I use and which exact stock rom image, the result is always the same: The normal update process failes with the messages according to my initial screenshot. Then, when doing factory Reset and reboot, it fails again. Repeating those steps (Factory Reset and Reboot) multiple times eventually works and the ROM boots up. This is good in terms of a phone on stock rom is better than a bricked phone. I am still wondering if that might even be a hardware issues which does not let me update it just in a normal way. Or something with EFS, no idea.
Unfortunately I am NOT able to get TWRP to work. I am simply checking that OEM unlock is enabled and then i flash using ODIN / AP the latest (also tried some older version) TWRP - the latest version is twrp-3.2.1-0-dream2lte.img.tar. This leads to the phone neither booting to TWRP (holding VolUp, Bixby and Power) nor to boot normally any more. And this means I have to redo the above steps to flash Stock rom again, which takes 1-2 hours every time.
Again, stock rom is better than bricked, but really I would like to go back to rooted custom rom to be able to use Titanium backup and other stuff.

I dont know why, but after several attempts to flash TWRP I managed to get it running and with that part done it was no problem to install Custom ROM and everything works now. Thanks for your help!