GT-N8000 downgrade and no update. - Galaxy Note 10.1 Q&A, Help & Troubleshooting

I've been using Gnabo v_7 version for quite a long time, and a very simple and beautiful day when I woke up my Samsung GT-N8000 was stuck on bootscreen. I wasn't able to do much so I got this "Brazil stock rom" that I found in a website, and it flashed all right, except for the detail that there is something at the screen that I haven't got a bloody clue how to remove. hahaha
And still, whenever I try to install another room, I got stuck at bootlogo and so on. I'm kinda lost here, mind a little help?
I traveled around the forum but well, I'm a little dumb so I couldn't find any proper information about, how to solve this. I would like to know if there is a way to remove this thing from the main screen, and post here the image for you guys to see it please.
I tried to post the image here to make it easier understanding, but since I got this login recently I can't =\
Thanks

Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.

DroidTwe4kz said:
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
Click to expand...
Click to collapse
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\

vitortakeda said:
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
Click to expand...
Click to collapse
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip

DroidTwe4kz said:
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
Click to expand...
Click to collapse
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!

vitortakeda said:
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
Click to expand...
Click to collapse
Here is tutorial about how to install ADB and Fastboot drivers and use them. Unfortunately, I don't know how to use it to restore efs. Sorry.

Related

[Q] HTC One S(ville) black screen, thats it... just a black screen, what can i do???

I was working fine, enjoying my new HTC One S with CM9 rom installed. Well the battery life wasnt the best on it, and i didnt install the custom kernel. So I looked for the custom kernel download(on my phone, not on my computer) and i found a .zip file. Well I thought that you could just download the kernel straight to my phone and open it up with "Rom Manager" which i did, it than said i needed to reboot the phone in recovery to continue the installation, so I did... it took me to recovery "to continue the installation" well than I looked away, looked backed down and it was black.... and i have tried powering up, booting into boot loader, booting into recover, and nothing... its just BLACK! nothing works, its literally useless ATM. I really messed up, is there anyway to fix this? Thanks in advanced!
----EDIT----
I think I accidentally flashed the kernel like i would normally flash a rom.... cause i downloaded the .zip file(directly to my phone, not using a computer), than i tapped the download and it asked me if i wanted to open it up with rom manager, so i did. and i think rom manager thought i was flashing a rom, when i wasnt, it was a kernel.... am i screwed? or is there anyway out of this?
Do you know the exact kernel you flashed--where did it come from
Some you need to extract and push
Assume you just tried to boot into bootloader thru phone buttons
Does your pc recognize your phone when plugged in, if so can you open a command window and try to access phone as in adb devices then adb reboot bootloader
assuming you are familiar with sdk adb/fastboot comands
otherwise i don't know what else to say--may be bad--sorry
Came from an XDA thread
Here is where it came from: http://forum.xda-developers.com/showthread.php?t=1708676 from "sun90" (half way down the page "CM9 KERNEL remix edition.zip - [Click for QR Code] (5.53 MB, 9 views) ")
i downloaded that straight to my phone and opened it up with Rom Manager, which i think the app took it as a rom, and installed it like a rom even though it was not a rom. I just tried to access it through adb, it comes up with no devices my PC does recognize it when i plug it in though...
Ive tried to get into bootloader tons of times, it just stays black... :'(
Thanks for your answer!
You flashed a galaxy s2 kernel on your one s? why would you ever think that was a smart thing to do?
Looking at the updater script in that zip it seems it wipes some partitions, the partitions on a SGS2 and the ONE S are different, so if that script accidentally wiped say the hboot partition, or some other critical-for-boot partition, you have a fully bricked phone.
For any devs that may know what partitions are what on the One S, the script wiped
mmcblk0p7, and wrote a zimage to mmcblk0p5
---EDIT---
Normally this is a cwm flashable zip on the Samsung Galaxy S II, which is why rom manager flashed it, as it met all the requirements, the only issue is, it was not made for the ONE S and probably overwrote some important things.
I tried for hours and hours to fix the same issue on a friend's One S (same symptoms, not same cause) to no avail. I tried QPST and telnet and a ridiculous amount of things. Had to bring it to the store and get a new one.
Good luck, but I don't believe there's anything you can do to fix it.
Just answered your question in the help thread, Didnt see this thread too !
Im afraid its not looking good, I think your best bet would be to call your provider and blame it on an OTA update.
And hope for the best
Alright, thanks for the help!
Well it looks like i bricked my phone than.... I thought that CM9 was only on the One S, so I just looked for the CM9 kernel, which obviously was for the sg2, i feel like such a dumb ass now! haha well thanks for all the help guys! ill be heading to the t-mobile store today to blame it on a OTA:]
yeah, others wont agree with what your about to do but........
just act like a complete noob, dont mention anything about software / firmware / ROMs / bootloader etc ect
just say your phone made a noise, you selected update and it died lol
good luck--I know it is heartbreaking
not sure of your situation with carrier, but you could go thru Retention if needed
Hi peeps.
i'm very new to all this but sort of know the basics
i'm running on Axiom now but tried to flash cm10 but after install i got a black screen so had to do a restore.
Today i just flashed venom and after the instal process is done, i hear the start up music but nothing on the screen.
I have had 3 other roms on my phone and never had a problem!
these are the steps i do
download rom - place on sd
put phone in recovery
reset factory
reset cache
install from sd
when it finish's reboot
blank screen.
Am i missing something?
Any help would be great and i can't post on the thread because i'm a noob with less than 10 and dont want to spam my way to the 10 :silly:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
rugmankc said:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
Click to expand...
Click to collapse
Thanks but i think that is now the least of my problems!
I used Goomanager and installed CM10, When I did it i installed teamwin recovery. It started to do a lot of strange things, when it finally rebooted i got a load of errors "phone is not working" nearly every 10 seconds?
it will not connect via usb, i discovered the the SD was not mounted.
I tried to mount the SD but it doesnt work, so i rebooted to recovery and tried to mount there but its coming up with - error unable to mount? ive tried everything but no joy
please please help
Thanks:crying:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
rugmankc said:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
Click to expand...
Click to collapse
I've got a mac
not sure what fastboot is.
I'll check out the link, and thank you very much for trying to help:good:
sorry i do know what fastboot is, yes can get in to it. but ive gone from CWM to teamwin recovery if i go in to the recovery section but that wont let me do anything because the mount. cant even load the phone up
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
rugmankc said:
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
Click to expand...
Click to collapse
im going to use someone elses alp top with windows. i'll ytry the all in one thing because thats how i rooted it in the first place. thanks for helping it means alot
good luck on it

Trying to update twrp..."trying"

I was trying to update this Nexus S, used to be mine but gave it away to someone, now is back and I was trying to update the whole thing, recovery, Os, yet I can't find a proper way to update the recovery and also I have Win8...when I got this phone rooted I had a Win7 machine, life was great, now with Win8 some things seem far from easy.
So I wonder if any kind soul could assist me as to lend me a hand about updating TWRP 2.3 to 2.7 so I can install a fresh rom, i have tried TWRP manager (useless as it can't find the proper device), Flashify is useless also as it can't find the img file and only shows TWRP 2.1 (why the fk do I need 2.1 when I have 2.3 ?), and Rashr is no good (it simple doesn't do anything at all... )
Any help is welcome.
fenrry said:
I was trying to update this Nexus S, used to be mine but gave it away to someone, now is back and I was trying to update the whole thing, recovery, Os, yet I can't find a proper way to update the recovery and also I have Win8...when I got this phone rooted I had a Win7 machine, life was great, now with Win8 some things seem far from easy.
So I wonder if any kind soul could assist me as to lend me a hand about updating TWRP 2.3 to 2.7 so I can install a fresh rom, i have tried TWRP manager (useless as it can't find the proper device), Flashify is useless also as it can't find the img file and only shows TWRP 2.1 (why the fk do I need 2.1 when I have 2.3 ?), and Rashr is no good (it simple doesn't do anything at all... )
Any help is welcome.
Click to expand...
Click to collapse
Google "Nexus Root Toolkit". Works great with Windows 8.1.
rhyang said:
Google "Nexus Root Toolkit". Works great with Windows 8.1.
Click to expand...
Click to collapse
I found something after a lot of searching and reading around back and forth on different places, thanks, I will keep it in mind anyway cause right now there is not that many sources for info on Nexus S.
fenrry said:
I found something after a lot of searching and reading around back and forth on different places, thanks, I will keep it in mind anyway cause right now there is not that many sources for info on Nexus S.
Click to expand...
Click to collapse
I have uploaded TWRP v2.8.0.1 flashable zip. Flash it like any normal ROM in the existing recovery.
Link: http://forum.xda-developers.com/showpost.php?p=55616780&postcount=115
Also, let me if you need help in installing drivers in Windows 8. I too am using Nexus S on Windows 8.1
smit.sanghavi said:
I have uploaded TWRP v2.8.0.1 flashable zip. Flash it like any normal ROM in the existing recovery.
Link: http://forum.xda-developers.com/showpost.php?p=55616780&postcount=115
Also, let me if you need help in installing drivers in Windows 8. I too am using Nexus S on Windows 8.1
Click to expand...
Click to collapse
Thanks so much fo the Zip, is way easier to just have this done via TWRP/ZIP, than trying to install drivers and so on, it becomes a pain when one thing fails and then u have to start downloading files drivers and more.
Now I'll just start checking roms!
fenrry said:
I was trying to update this Nexus S, used to be mine but gave it away to someone, now is back and I was trying to update the whole thing, recovery, Os, yet I can't find a proper way to update the recovery and also I have Win8...when I got this phone rooted I had a Win7 machine, life was great, now with Win8 some things seem far from easy.
So I wonder if any kind soul could assist me as to lend me a hand about updating TWRP 2.3 to 2.7 so I can install a fresh rom, i have tried TWRP manager (useless as it can't find the proper device), Flashify is useless also as it can't find the img file and only shows TWRP 2.1 (why the fk do I need 2.1 when I have 2.3 ?), and Rashr is no good (it simple doesn't do anything at all... )
Any help is welcome.
Click to expand...
Click to collapse
Hi There,
The latest Recovery for Nexus S is TWRP v2.8.x. Well u will need to flash the Twrp v2.8.x using fastboot because if you try installing the recovery using the TWRP Manager it will crash. I have a guide on how to root nexus s in the nexus s development section..Go through it . If you have a rooted Nexus S then skip to contect showing how to flash a custom recovery using Fastboot in my guide go through it and Enjoy..
Happy Flashing.
Good Luck
fenrry said:
I was trying to update this Nexus S, used to be mine but gave it away to someone, now is back and I was trying to update the whole thing, recovery, Os, yet I can't find a proper way to update the recovery and also I have Win8...when I got this phone rooted I had a Win7 machine, life was great, now with Win8 some things seem far from easy.
So I wonder if any kind soul could assist me as to lend me a hand about updating TWRP 2.3 to 2.7 so I can install a fresh rom, i have tried TWRP manager (useless as it can't find the proper device), Flashify is useless also as it can't find the img file and only shows TWRP 2.1 (why the fk do I need 2.1 when I have 2.3 ?), and Rashr is no good (it simple doesn't do anything at all... )
Any help is welcome.
Click to expand...
Click to collapse
Hi there,
i just made a .doc in which i have briefly described how to flash twrp on nexus s just download the file and go through it.
Thanks!, I forgot to reply about this, I managed to get things working, I really don't know how it happened but after repeating the steps several times something must have kicked and things finally worked.
fenrry said:
Thanks!, I forgot to reply about this, I managed to get things working, I really don't know how it happened but after repeating the steps several times something must have kicked and things finally worked.
Click to expand...
Click to collapse
Ok Brother, Chill and Enjoy.

[Q] Lg Ls620 (realm) custom recovery

I was trying to find a custom recovery, or any recovery that will work on my lg realm. I boot recovery and it gives me a error message so im guessing its either wiped out or blocked...any ideas out there on how to correct or replace it
twtoned said:
I was trying to find a custom recovery, or any recovery that will work on my lg realm. I boot recovery and it gives me a error message so im guessing its either wiped out or blocked...any ideas out there on how to correct or replace it
Click to expand...
Click to collapse
Looking for one as well. I have not found one.
Recovery is actually preinstalled
I found this just tooling around. Use your favorite file browser, I used
Total commander. /system/vender/itson
The zip file is there. Hope this helps. (Rooted LG ls620)
Could you explain in a little better detail on what you mean Enigmatic177... I'm pulling my hair out Hehe
If anyone makes or finds a working recovery please post it.
Itson is a zip file that was installed after last update it has the basics to unlock the boot loader. I unpacked it used Rom toolbox pro rebooted to RECOVERY did regular reboot system upgraded.
A couple if bit mapp errors 11111. Then I basically flashed CWM.
Before you do this the partitions change from ext2-ext4. I'd advise
Backing them up.
LG Realm & exceed 2 TWRP recovery/fastboot files
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
TWRP recovery help L620 LG Realm
hello I followed the steps in the read me file and i succeeded in installing twrp although im having troubles booting up to my system os. when i power on my device it takes me straight to twrp. i have a feeling i might of missed a step. i tried creating a backup but i cant because i noticed my screen turns off fast. do you think you might know what might be the problem why i cant boot up to my os? thanks!
I think i know what seems to be the problem. I think i might have accidentally replaced the boot img with the twrp recovery img. i did not make a backup before this happened. is there anything i can do to make my phone boot up to its normal image? thanks
Nope. It is officially a paperweight and no one I know of has access to the stock ROM either.
Sent from my LGLS620 using XDA Premium 4 mobile app
Hey
Has anybody found a custom rom?
Finally. Easy as pie
Ok, I downloaded an image (w5c_twrp_bumped.img)
put that img on the root of my sd card
downloaded Rashr from the google play store
opened rashr and tapped 'recovery from storage', navigated to external sd and tapped the image and tapped
ýes please'
flashed it. after the flash the phone rebooted into the twrp recovery.
then just rebooted back into the system
worked perfectly.
im new here im not allowed to post outside links yet, just google "w5c_twrp_bumped.img" should take you to a link for a download of that recovery
i got twrp now as a custom recovery. on my lg realm.
That_One_Person760 said:
hello I followed the steps in the read me file and i succeeded in installing twrp although im having troubles booting up to my system os. when i power on my device it takes me straight to twrp. i have a feeling i might of missed a step. i tried creating a backup but i cant because i noticed my screen turns off fast. do you think you might know what might be the problem why i cant boot up to my os? thanks!
Click to expand...
Click to collapse
You have the bumped recovery so all i can say if u messed up is to flash a stock rom u can find on google i had to re flash mine a few times messing with root
right on, thanks for the info. I had no problems at all. it all fell in place like i was hoping. The Realm is the easiest device Iv ever rooted, flashed, and messed with. Well, as far as rooting and flashing a custom recovery. dunno bout roms though. Im sure its simple?
The_android_Modder said:
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
Click to expand...
Click to collapse
OK, I grabbed and extracted this. I used Flashify to simply flash the recovery (w5c_twrp_bumped.img) and it works like a dream on my LG Realm.
OTOH, trying the same on an Exceed 2 gets me TWRP, but it cannot mount much of anything and the backup fails. After failing, it tells me "No OS found, continue?" I continue and get the message "Appears your device has no Root, install now?' I am absolutely certain I have root, or wouldn't even be able to run Flashify, so I continue and it simply boots into the OS just fine. Perhaps the readme isn't complete, as I see the following file in the extracted folder (resources.zip) with no explanation of why it's there. It "appears" to be a flash-able zip that installs "itson" (whatever THAT is). Note that the Realm has this in the /system/vendor/itson, yet the Exceed 2 doesn't.
Have you actually used this on an Exceed 2? And if so, what am I missing here?
The_android_Modder said:
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
Click to expand...
Click to collapse
Link is DEAD. Any chance you can reupload this file? I can't make heads or tails of some of this thread and I don't want to destroy this phone. Thanks!!!
petermg said:
Link is DEAD. Any chance you can reupload this file? I can't make heads or tails of some of this thread and I don't want to destroy this phone. Thanks!!!
Click to expand...
Click to collapse
I'll do you one better. Just forget about the post you replied to, as it's convoluted as hell. Install TWRP 2.8.6 from here. Ignore the big red warning about the Realm, as he evidently hasn't updated the OP. You can view my notes regarding the Realm in this reply. Tested several times and verified working better than anything else available. Easiest recovery to install I've ever dealt with (all done with an .apk). The option to access via cold boot (battery pull procedure) is something to behold
Be sure to thank the developer, even if you need to create an account to do so. Very VERY nice work!
fathergweedo said:
I'll do you one better. Just forget about the post you replied to, as it's convoluted as hell. Install TWRP 2.8.6 from here. Ignore the big red warning about the Realm, as he evidently hasn't updated the OP. You can view my notes regarding the Realm in this reply. Tested several times and verified working better than anything else available. Easiest recovery to install I've ever dealt with (all done with an .apk). The option to access via cold boot (battery pull procedure) is something to behold
Be sure to thank the developer, even if you need to create an account to do so. Very VERY nice work!
Click to expand...
Click to collapse
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you replied I installed the version 2.8.5 from here:
http://androidforums.com/threads/twrp-2-8-5-0-for-realm-ls620-and-exceed-2-vs450pp.908704/
Is 2.8.6 better? Looks like the 2.8.5 can't be booted into via key combo from power off? Are there any other differences? I just used the Rashr flash tool from the market to flash 2.8.5. Worked flawlessly. This is actually my mom's phone and it wanted to do a system upgrade but I wanted to back it up first so that's the reason I wanted a recovery.
Pretty cool though, this recovery installs just via an APK!!!? That's amazing!
I'm tempted to install this on her phone next time she comes over... it should be fine right?
Thanks again!!!!!!!!!!
petermg said:
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you replied I installed the version 2.8.5 from here:
http://androidforums.com/threads/twrp-2-8-5-0-for-realm-ls620-and-exceed-2-vs450pp.908704/
Is 2.8.6 better? Looks like the 2.8.5 can't be booted into via key combo from power off? Are there any other differences? I just used the Rashr flash tool from the market to flash 2.8.5. Worked flawlessly. This is actually my mom's phone and it wanted to do a system upgrade but I wanted to back it up first so that's the reason I wanted a recovery.
Pretty cool though, this recovery installs just via an APK!!!? That's amazing!
I'm tempted to install this on her phone next time she comes over... it should be fine right?
Thanks again!!!!!!!!!!
Click to expand...
Click to collapse
That one will cold boot with the battery pull procedure too. A little further down that thread you'll see I modded it to work correctly with the Exceed 2 in addition to the Realm. I like the 2.8.6 better if only that the dates of the backup are correct now. The 286.apk will work fine and overwrite your current recovery. If you leave it installed, you can always open it and reboot to recovery from within the app. If I have more time I'll post a screenshot, but running late for work. I think the screen dimming/timeout issue was fixed as well, but I haven't verified that. I normally disable that in TWRP anyway, as I like to monitor what it's doing during a backup/restore in case of errors.
fathergweedo said:
That one will cold boot with the battery pull procedure too. A little further down that thread you'll see I modded it to work correctly with the Exceed 2 in addition to the Realm. I like the 2.8.6 better if only that the dates of the backup are correct now. The 286.apk will work fine and overwrite your current recovery. If you leave it installed, you can always open it and reboot to recovery from within the app. If I have more time I'll post a screenshot, but running late for work. I think the screen dimming/timeout issue was fixed as well, but I haven't verified that. I normally disable that in TWRP anyway, as I like to monitor what it's doing during a backup/restore in case of errors.
Click to expand...
Click to collapse
THANKS!!!! I'll make it a point to flash that to my mom's phone next time I get the chance!

[Q] Rooted with Recovery Now What???

I have an unlocked xperia z3 d6603 I bought brand new in january I believe. I just today rooted and installed recovery but am stuck on the 23.0A.2.93 tft rom which it shippped with. It would have normally been running unrooted the latest rom from sony which was just pushed out a couple months ago. I'm in california and need a rooted d6603 generic global rom, or even unrooted, and I can't seem to find the down link here. In xpreifirm 3.6a latest, I keep getting a java error so can't use that and I've already uninstalled and installed the latest 64bit java8 update 40. I was going to just flash it with the moonwalker rom but it days I need to be on a different tft altogether. Any help here would be appreciated. I have installed a firewall, changed dns servers, and uninstalled a few things using rom toolbox. Hoping to just update it to the recent tft or even better, a working custom rom which won't mess up the default phone capabilities. I'm on kitkat 4.4.4, at&t lte, rom 23.0.A.2.93
Again I need a rooted global generic 577 tft for a z3, a nonrooted one, or even better, a custom one I can just flash to it so I can get back to my life.
since you have a working recovery just flash this one 23-0-1-5-77-deodexed-zipaligned it's the latest KK
ps: I'm on AT&T in CA as well and running that firmware just fine for a while now, it's generic global so no worries...
awesome. THANKS. Gonna try it now. Been at it all day from like 10am to about 5 when I had to break
How do you flash a zip file
tweker said:
awesome. THANKS. Gonna try it now. Been at it all day from like 10am to about 5 when I had to break
Click to expand...
Click to collapse
I rebooted with TWRP in recovery mode, reset device (Wipe Data, Cache and Dalvik Cache), saw no way of flashing from recovery mode. Shut phone off. Plugged in in flash mode with the zip file in the firmwares folder and it was not recognized by flash tool. Where are the directions for flashing a zip?
Choose the second option in recovery
Install custom zip
I used NDR to reboot into recovery. The zip was on both internal and external at root. First time I selected the one from internal and it gave no errors. Wiped cache and rebooted and still on stock 93. Did the exact same thing again choosing zip on sd card and it still says 93. Third time I did it from sd card but no cache wipe. Still on23.0.A.2.93. WTF???
Where can I find a working ftf. NDR doesn't work for ****. BTW, phone is setup in dev mode with mock, airplane mode etc with supersu free working. I think
BTW, why in the hell does the thread with all the roms not have any current ones???? rooted or not
What for are you trying to flash? Please provide a link.
What does the recovery log say? It really helps if you tell us this.
FTF files are geberally not uploaded anymore as it is very easy to download any you want from the sony servers and create your own FTF using flashtool and Xperia firm.
Ps, it may be nice to watch your language. The issue is not NDR, it works fine.
I'm using D6603_23.0.1.A.5.77_deodex.zip from here: http://forum.xda-developers.com/z3/development/deodex-23-0-1-5-77-deodexed-zipaligned-t3015178 on top of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf which was rooted and dual recovered. I have flashed the above 5.77 zip file like 5 times from recovery mode and still on 93. This last time I noticed I had no file mgr. Installed es, mounted system rw like it says to do after root, reflashed the 77 deodexed zip, wiped dalvik and cache, reupdated supersu zip in recovery, rebooted, and stil on93. What am I doing wrong? Is there not a dern ftf file I can use instead? OR, should and could I just wait for another official update?
tweker said:
I'm using D6603_23.0.1.A.5.77_deodex.zip from here: http://forum.xda-developers.com/z3/development/deodex-23-0-1-5-77-deodexed-zipaligned-t3015178 on top of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf which was rooted and dual recovered. I have flashed the above 5.77 zip file like 5 times from recovery mode and still on 93. This last time I noticed I had no file mgr. Installed es, mounted system rw like it says to do after root, reflashed the 77 deodexed zip, wiped dalvik and cache, reupdated supersu zip in recovery, rebooted, and stil on93. What am I doing wrong? Is there not a dern ftf file I can use instead? OR, should and could I just wait for another official update?
Click to expand...
Click to collapse
That is not a ROM file, it does not contain a ROM. It just deodex's your system files if you are on that firmware.
And, No, there is not a FTF you can flash that is rooted. FTF files have to be completely stock as we cannot sign them with Sony's keys as we do not know them. The only way to flash something rooted is via recovery
Post#2 told me I could flash the zip over and it would work. No wonder it doesn't work because it doesn't do anything. I don't want to unlock boot because I may fail official updates. I really just want to update to a working global generic 77 rooted dual recovered system. So basically even if I had the official 77, unrooted, I still couldn't use (nor root) it right? Thanks for the help. I at least know to go another route.
tweker said:
Post#2 told me I could flash the zip over and it would work. No wonder it doesn't work because it doesn't do anything. I don't want to unlock boot because I may fail official updates. I really just want to update to a working global generic 77 rooted dual recovered system. So basically even if I had the official 77, unrooted, I still couldn't use (nor root) it right? Thanks for the help. I at least know to go another route.
Click to expand...
Click to collapse
Post #2 is wrong. Also the thread stated in the first line that a requirement for that to work is that you are already on .77 firmware.
There is no need to unlock your boot.
Just flash a .77 prerooted ROM.
If you cannot find one then make one yourself. Follow the guide in the thread called PRFCreator (Just google it)
Once you have the files downloaded it takes 7 minutes and it is all automated for you
Thank You Very Much. At present I have access to two pc's. One is my roomies (win8.1) and mine (win7). My roomies has some sort of java issue and xperifirm fails right when you click the file you want. Tried fixing java didn't work. Mine is wireless, dns disabled, mac changed, hosts file, and tiny wall fw. Experifrm says no net access even though it works fine. Tried a cable and for the life of me got the same error (couldn't quite reconfigure it to work correctly-pita). If I ever get the file I will do the prfcreator magic, and I'm assuming, flash it through ndr tools in recovery mode. In the mean, I might request an xda user in another thread to grab one for me and post it. Should help lots of people not just me. Again, thank you for your help, saved a lot of hair pulling.
tweker said:
Thank You Very Much. At present I have access to two pc's. One is my roomies (win8.1) and mine (win7). My roomies has some sort of java issue and xperifirm fails right when you click the file you want. Tried fixing java didn't work. Mine is wireless, dns disabled, mac changed, hosts file, and tiny wall fw. Experifrm says no net access even though it works fine. Tried a cable and for the life of me got the same error (couldn't quite reconfigure it to work correctly-pita). If I ever get the file I will do the prfcreator magic, and I'm assuming, flash it through ndr tools in recovery mode. In the mean, I might request an xda user in another thread to grab one for me and post it. Should help lots of people not just me. Again, thank you for your help, saved a lot of hair pulling.
Click to expand...
Click to collapse
Sorry about the confusion, indeed the first link that I provided was just a patch to deodex your room (I always use deodex so I can mod my rom)....anyway you can use this one it's a generic prerooted .77 from the z3 android development section in this forum, then you can patch it with the other one if you have the need to...just follow the instructions in this link and you should be on your way
Again sorry about that first post, I rooted my phone the minute root was available on locked bootloader so it's been some time now
I have been to that link. The only one I can see that says generic global is the 23.0.A.2.93 one. The others say, Generic_DE, Generic_NCB, or Generic_AU. Which looks to me like Deutch, Generic Nordic?, and Australian? Since I speak english and am nowhere near any of those places, I did not touch them. Which one is safe to use and will there be any post config for my locale and radios?? Plus I have no clue what the purpose is of de-odexing the file system (flashing that zip) does. I still have read write issues with apk's I install when I tell them to use my 128gb sd card. I did recover my setup prior to the zip flash you pointed me to which I still have-thank you.
tweker said:
I have been to that link. The only one I can see that says generic global is the 23.0.A.2.93 one. The others say, Generic_DE, Generic_NCB, or Generic_AU. Which looks to me like Deutch, Generic Nordic?, and Australian? Since I speak english and am nowhere near any of those places, I did not touch them. Which one is safe to use and will there be any post config for my locale and radios?? Plus I have no clue what the purpose is of de-odexing the file system (flashing that zip) does. I still have read write issues with apk's I install when I tell them to use my 128gb sd card. I did recover my setup prior to the zip flash you pointed me to which I still have-thank you.
Click to expand...
Click to collapse
1) its called a FTF file not a TFT file. It's a FlashTool File.
2) your sd write card issues are a feature of KK, and nothing to do with any error or bug to do with your phone. Just Google KK write to sd card to read more about it and how to circumnavigate this issue that was deliberately introduced by Google.
3) i have read some of the advice you have banded about in several of the thread here. Some of it is just plain wrong. Although not dangerous to anyones device it may be worth reading and learning a bit more first.
4) please stick to asking questions in just one thread, there is no need to ask in several thread because the first time you did not get an immediate answer
5) you can safely flash a FTF from any region as long as it is for the same model you have. Especially as you are only going to be on that version for a few minutes whilst you root them immediately upgrade.
Ok, great. I'll grab the de one. As for not trying to help; I put down what worked for me. If I don't know everything I can still give input with the little I know. That's how people learn, myself incl. I just got my pc running not two weeks ago so a little overwhelmed with having just rooted as well. Thanks very much for all your help.
tweker said:
Ok, great. I'll grab the de one. As for not trying to help; I put down what worked for me. If I don't know everything I can still give input with the little I know. That's how people learn, myself incl. I just got my pc running not two weeks ago so a little overwhelmed with having just rooted as well. Thanks very much for all your help.
Click to expand...
Click to collapse
No worries. I did not mean to imply that you should not help, only that you should be sure that what you are saying is in fact correct information.
We do all have to learn, but its hard to learn when incorrect information is posted and stated as "fact"
Greg
From install to booted took 4 min. Just had to update supersu and remove a few things. This is awesome! NDR Utils is worth paying for. Now I can finally encrypt my phone. TYSM

Stuck in TWRP (Recovery)

Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
SlimeAndroid said:
Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
Click to expand...
Click to collapse
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
The "fix" that you used didn't help.it successfully flash, it only help you "force" the ROM to flash. You bypassed a safety measure that was designed to keep you from flashing the wrong thing, now you're dealing with the results of forcing it to flash on a device it wasn't meant for.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I'm sorry I may have linked the wrong page, either way on the website of the rom I downloaded the right thing, I'm sure about it because I checked it multiple times (the error I made in writing the post may be cause by me panicking, sorry :crying: ).
While waiting for answers I installed a different twrp and it WORKS! I'm so happy I could cry. Thank you nonetheless for your help (Still dunno what the problem was though xD)
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
____Mdd said:
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
Click to expand...
Click to collapse
If you read the post above yours, you'll see they solved the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
You always have to make sure the download is for your model of phone(settings -about) and always make sure the download has properly downloaded and I use md5 checksum as this verifies the download is not courupt.
Sent from my iPhone using Tapatalk

Categories

Resources