Related
Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...
antwong45157 said:
Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...
Click to expand...
Click to collapse
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload
Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
Woodyy said:
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload
Click to expand...
Click to collapse
Going to try to side load first with twrp. If all else fails gonna try cwm recovery
Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*
antwong45157 said:
Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*
Click to expand...
Click to collapse
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.
Woodyy said:
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.
Click to expand...
Click to collapse
I tried flashing paranoid android 3.94 which is android 4.3 with adb. Hoping it would work different . Nope same result.
I am able to get back on 4.2.2 using adb. I'm on 4.2.2 typing this message . I just need to find out why I can't get on 4.3 with getting stuck at boot screen
This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app
Jewveeski said:
This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I believe my boot loader is unlocked. When. I reboot I see he unlocked lock. But I did flash the new boot loader so maybe I would have to re unlock it? I will try the ROM you posted
Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!
itslels said:
Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!
Click to expand...
Click to collapse
I had the issue when I tried to go directly from 4.2.2 to a 4.3 custom. The only thing that cleared it up was flashing stock 4.3 from google. After that, no more problems.
Hmm wonder what could be causing it. I did have this issue going from 4.2.2 to 4.3. Every 4.3 ROM I have flashed has booted.
toro, toro!
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
i have the same fuking problem , what did you do ?
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Gz dude enjoy 4.3
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Thanks, I followed this and finally managed to get to 4.3
http://forum.xda-developers.com/showthread.php?t=2389721
Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
EDIT: I did a reboot when I got home and it booted up fine, although I felt like it took longer than on previous versions.
oynoy said:
Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
Click to expand...
Click to collapse
Gotta be able to reboot your phone brother lol. Give it a shot. If it locks up there is always a way to fix the issue... Good luck. Best wishes
FIX for issue getting stuck on google screen after 4.3 reboot
I don't know if anyone has posted this elsewhere. I had the same problem yesterday - after a lot of playing around this is how I fixed it:
***Note1: you need adb and fastboot.
***Note2: make external backup of things (i.e. photos) you want to keep using adb.
Procedure:
1. Download 4.2.2 image from google (can't post link because of spam prevention rules - you can search for "google developers nexus images")
2. extract files to location of choice
3. Download latest custom recovery image of your choice. I prefer TWRP (latest 2.6)
3. reboot to recovery, do a full factory reset (wipe everything, you will lose all your storage).
4. Reboot to bootloader (from phone off, power plus volume rocker).
5. flash stock image via fastboot (change names and paths acordingly):
Code:
fastboot devices (make sure fastboot can see your device)
adb reboot bootloader
fastboot flash bootloader bootloader-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio /path/to/radio-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio-cdma /path/to/radio-cdma-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot -w update /path/to/image-mysid-<version>.zip
5. After this last step, the phone should reboot.
6. Go through the phone setup process.
7. power off, and boot to bootloader
8. flash custom recovery:
Code:
fastboot flash recovery /path/to/custom-recovery.img
9 reboot to recovery. TWRP will ask you if you want to root when you reboot to system.
10. Phone rooted and like new!
I think that is all - you can flash your ROM of choice after this!
I am on 4.1.2
Ive used all 3 available custom recoveries, 4 if you include the other TWRP
Every recovery with every zip, all md5 checked, say unable to open zip
Am I doing something wrong?
shaunjohn said:
I am on 4.1.2
Ive used all 3 available custom recoveries, 4 if you include the other TWRP
Every recovery with every zip, all md5 checked, say unable to open zip
Am I doing something wrong?
Click to expand...
Click to collapse
What are you trying to flash?
And which recovery VERSION are you using?
Model aand name of rom
Which model do you have?? and what is the rom's name?
210r
ive tried
philz recpvery
cwm
twrp 2/7 and 2/8
ive tried
cm11
rocket
swat(name may be wrong)
kids
Reflash the 4.4.2 firmare from odin all over again and install TWRP (2.8.0.0) the flash rom in recovery
A friendly reminder - please keep all question threads in the Q&A board. Android dev is only for posting releases, not questions.
Thanks!
Same Result
ruzell said:
Reflash the 4.4.2 firmare from odin all over again and install TWRP (2.8.0.0) the flash rom in recovery
Click to expand...
Click to collapse
same result, error opening zip file
Did you ever figure this out? I"m having the same issue.
Can't flash a ROM on Tab 3 7.0 t210r
I am rooted, first thing I did after purchase.
Am currently running 4.1.2, build jzo54k.t210rueamk1
I have flashed PhilZ Touch 6, 6.44.9, ClockworkMod 6.0.4.9 from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi/
I have tried to flash the following ROMs:
Stockrom Series Ultimate Edition
http://forum.xda-developers.com/showthread.php?t=2489395
RocketTab v3.1
http://forum.xda-developers.com/showthread.php?t=2507772
Flash fails with:
Installation aborted (bad), can't open <path to zip file><name of zip>
This happens after a factory reset, wipe data, cache.
I have a Samsung S3 that I have rooted, and then flashed many times. Before that I had an HTC EVO. I am not new to the process, but apparently I am missing something here.
Got any suggestions?
Which Odin Version you are used to install The Recovery? Try an other Version.
Is your Rom on The micro Sdcard ? If you use Philz so is The max capacity 32 GB, if you use TWRP so is max 64 GB supported.
starmaha said:
I am rooted, first thing I did after purchase.
Am currently running 4.1.2, build jzo54k.t210rueamk1
I have flashed PhilZ Touch 6, 6.44.9, ClockworkMod 6.0.4.9 from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi/
I have tried to flash the following ROMs:
Stockrom Series Ultimate Edition
http://forum.xda-developers.com/showthread.php?t=2489395
RocketTab v3.1
http://forum.xda-developers.com/showthread.php?t=2507772
Flash fails with:
Installation aborted (bad), can't open <path to zip file><name of zip>
This happens after a factory reset, wipe data, cache.
I have a Samsung S3 that I have rooted, and then flashed many times. Before that I had an HTC EVO. I am not new to the process, but apparently I am missing something here.
Got any suggestions?
Click to expand...
Click to collapse
bierma32 said:
Which Odin Version you are used to install The Recovery? Try an other Version.
Is your Rom on The micro Sdcard ? If you use Philz so is The max capacity 32 GB, if you use TWRP so is max 64 GB supported.
Click to expand...
Click to collapse
I didn't use Odin to flash the recovery. Downloaded the zip and flashed via recovery.
I have tried with the ROM on the external and internal SD. Same results.
32GB SD.
starmaha said:
I didn't use Odin to flash the recovery. Downloaded the zip and flashed via recovery.
I have tried with the ROM on the external and internal SD. Same results.
32GB SD.
Click to expand...
Click to collapse
u
How do you rooted your Tab?
With Stockrecovery you can not flash a Rom or Recovery.
Flash Philz or TWRP With Odin, reboot to The New flashen Recovery , than you can install a Rom.
All information for The right steps you will find at dev Sektion.
bierma32 said:
u
How do you rooted your Tab?
With Stockrecovery you can not flash a Rom or Recovery.
Flash Philz or TWRP With Odin, reboot to The New flashen Recovery , than you can install a Rom.
All information for The right steps you will find at dev Sektion.
Click to expand...
Click to collapse
To clarify, when I initially rooted, I used Odin to flash recovery and root.
starmaha said:
To clarify, when I initially rooted, I used Odin to flash recovery and root.
Click to expand...
Click to collapse
At first we are turn us i The circle,but now we can come to your prob.
Flash a Rom and make a picture and post that here. So we can See The error message and your Recovery.
starmaha said:
To clarify, when I initially rooted, I used Odin to flash recovery and root.
Click to expand...
Click to collapse
Sounds like the rom download is bad. Check the md5 of the rom before trying to install.
Kind of success. I downloaded the same version of PhilZ, for Odin, on my laptop.
I put the tablet in download mode and flashed the recovery with Odin.
I downloaded the ROM again (http://forum.xda-developers.com/gal...m-stockrom-kitkat-version-16-08-2014-t2849742). This is one I had tried before. This time to my laptop and copied it to the tablet. The other times, I had downloaded the ROM directly onto the tablet.
While it was in the process of flashing, there were some video anomolies.
I rebooted the tablet into recovery and flashed the ROM. It hung on SAMSUNG for a very long time after the flash and reboot. I powered it off and rebooted. It booted completely this time, but not without some issues. The first thing was when the message pops up that Android is optimizing apps. That bar was all screwy looking, snowy. (see attached image)
Once I got to the lock screen and entered the pin, the screen "fractured", pieces shifted around, and the tablet locked up. I wish I had taken a picture of it. Never seen anything like it.
I had not done a data wipe yet. I did a data wipe, rebooted, entered the pin, tablet locked up again.
I then was going to restore the backup I made before the flashing. It wouldn't restore because of an MD5 mismatch. I had restored this backup previously with no problem.
I restored an older backup and then spent a couple of hours getting everything back to the level of the now broken backup.
Flash nolekat and all went fine.
I've had problems as well. I normally flash via a recovery. At times I'll have an md5 mismatch or it just doesn't work; I've even backed up a working ROM only to find out I can't restore the same backup. Seems like a hit or miss with me
I tried flashing NoleKat and it failed on me too.
[/COLOR]
bierma32 said:
At one of your post you write after flashing you must put in the Pin?
So you have make not a clean install or factory reset, you done a wipe cache and wipe dalvik.
You must do a clean install if you come from different Roms or Version.
Click to expand...
Click to collapse
Please post a picture from your Recovery with the error message.
After 3 yrs on custom ROMs, I've managed to screw up my Note 2, and I'm lost as to how to restore my phone.
I've been on the Jedi Touchwiz ROM for ages, and about a year ago, changed over to Cyanogen.
I went from the Cyanogen 0825-Nightly to the latest 1017-Nightly by:
-backing up my data in Titanium Root,
-going into Recovery and doing a Wipe Data/Factory Reset,
-install the new 1017-Nightly image
-install GAPPS for Android 5.1
then reboot.
All is good on reboot, and I enter my Google info, mount desktop. I then install the Titanium Root app, and it reports that I've lost Root.
So I try to update SuperSU, and it fails to do it directly, and trying to do it with CWM Recovery fails as well.
I then use Recovery to Wipe Data/Factory Reset again,
reinstall 1017-Nightly and GAPPS 5.1
and reboot, thinking I must have missed something.
Now... I'm stuck on the Cyanogen Loadscreen (pulsing Blue Head). I haven't let it go longer than 10mins, but I don't think it should take that long.
I tried going back to my 0825-Nightly after this point, and no luck, I'm stuck on the Loadscreen.
Here are my questions:
1. I do not understand what being stuck on the Loadscreen means... what do I need to fix? Can I do it via Recovery?
2. How do I obtain Root again? The methods I originally used were for Jellybean... are there updated methods now?
3. What prevents SuperUser from updating?
Thanks for any help guys... I need my phone back!
on your second attempt you got stuck on boot screen??
i think you can wait for some more time and check..
remove battery re-insert and check whether it boots or not.. or else do a factory reset n check whether it boots or not..
if not do a factory reset and re flash the CM to check.
. if all failed then flash n7100 stock firmware via odin ..
about rooting.. if you have a custom recovery you can try to re root via custom recovery.. simply flash supersu.zip in your custom recovery...
https://download.chainfire.eu/696/SuperSU
Hi Tornado,
BTW, Tornados, esp the IDS variant, are great planes. Nice to see your avatar :good:
I had a comment from elsewhere, so I tried this:
-wipe data/factory reset inside CWM Touch Recovery
-formatted /system partition
-installed the 20151007 CM 12.1 Snapshot
-installed GAPPS 5.1
and then let it reboot. LOL, I've been worried about screen burn in, but I left it run for over an hour... no joy. It never left the loadscreen.
Just for grins, I tried the older CM11 version, and whilst the loadscreen problem still persisted, I did recognize the older boot animation.
At this point, am convinced I have soft-bricked the phone, since I have Recovery and Bootloader (thank goodness) still working, but something else is either not clearing or is corrupted.
I'm definitely thinking about flashing stock firmware again, but not sure if I should go back to Jellybean? or find an Android 5 image?
Am also looking into ADB commands to see if there is something deeper I can flush out, but I really don't want to make things worst.
I'm hoping that someone else has run into a similar situation... cheers for your suggestions!
tornado92 said:
on your second attempt you got stuck on boot screen??
i think you can wait for some more time and check..
remove battery re-insert and check whether it boots or not.. or else do a factory reset n check whether it boots or not..
if not do a factory reset and re flash the CM to check.
. if all failed then flash n7100 stock firmware via odin ..
about rooting.. if you have a custom recovery you can try to re root via custom recovery.. simply flash supersu.zip in your custom recovery...
https://download.chainfire.eu/696/SuperSU
Click to expand...
Click to collapse
Enter custom recovery.. and find mount and unmount area.. and select mount system then restart phone n tell me result
I went into Recovery:
-selected Mount System
-Reboot
Phone stayed on Loadscreen for 30 mins. After that, I yanked the battery.
I'm going to go into Bootloader, and swap out CWM for TWRP to see if that makes a difference. If any changes, will report back.
tornado92 said:
Enter custom recovery.. and find mount and unmount area.. and select mount system then restart phone n tell me result
Click to expand...
Click to collapse
UGH. Still no joy.
Changed out CWM Recovery to TWRP,
-did Full Reset
-Advanced Wipe of System, Data, Int Storage
-install 1007 Snapshot of CM12.1
-install GAPPS 5.1
then reboot.
After 35mins of loadscreen, yanked the battery.
I can change Recovery images like a Boss now at least :silly:
motionmonk said:
I'm going to go into Bootloader, and swap out CWM for TWRP to see if that makes a difference. If any changes, will report back.
Click to expand...
Click to collapse
Best option for you now is to unbrick your device to official stock firmware... and then try to install custom rom again... i can make ur device boot normally at this stage.. but ur phone will boot on factory imei..meaning wont detect sim .. so first unbrick your device to be at safer place to avoid further corrupting the efs.. hahahaaa
---------- Post added at 12:05 PM ---------- Previous post was at 11:56 AM ----------
Install official firmware.. and enter stock recovery.. and try to reeset ur phone.. if u get a error code e/failed.to.mount efs.. ur efs is.messed up which is preventing ur phone from booting.. but if dont get any error your phone will boot normally
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
tornado92 said:
Best option for you now is to unbrick your device to official stock firmware... and then try to install custom rom again... i can make ur device boot normally at this stage.. but ur phone will boot on factory imei..meaning wont detect sim .. so first unbrick your device to be at safer place to avoid further corrupting the efs.. hahahaaa
---------- Post added at 12:05 PM ---------- Previous post was at 11:56 AM ----------
Install official firmware.. and enter stock recovery.. and try to reeset ur phone.. if u get a error code e/failed.to.mount efs.. ur efs is.messed up which is preventing ur phone from booting.. but if dont get any error your phone will boot normally
Click to expand...
Click to collapse
Keep updating me. I will guide u further
Just so I don't dig a deeper hole, I want to clarify a few points...
1. by going back to stock firmware, do you mean a certain OS version? If I find a stock Android 5 version, is that ok? or would going back to like Jellybean be better?
2. you mentioned that the factory imei will not detect my sim, so the radio won't work? If so, there is a way to fix this?
3. again for stock firmware... my phone is an American N7100 GSM (T-Mobile) version. About 2 years ago, it became an Int'l N7105 LTE mod, since I liked the feature set more, plus one of my past ROMs (Jedi-X?) I think changed it to the N7105.
-should I go back to a pure N7100 stock firmware, or a N7105 firmware?
Will start looking for firmware options in the meantime.
tornado92 said:
Best option for you now is to unbrick your device to official stock firmware... and then try to install custom rom again... i can make ur device boot normally at this stage.. but ur phone will boot on factory imei..meaning wont detect sim .. so first unbrick your device to be at safer place to avoid further corrupting the efs.. hahahaaa
Install official firmware.. and enter stock recovery.. and try to reeset ur phone.. if u get a error code e/failed.to.mount efs.. ur efs is.messed up which is preventing ur phone from booting.. but if dont get any error your phone will boot normally
Keep updating me. I will guide u further
Click to expand...
Click to collapse
There is no 5.0 stock firmware for n7100 . Latest is 4.4.2 if your phone model is n7100 in download mode. Then your phone isnt tmobile.. and about factory imei .. first unbrick your device to check the status of your imei.. it could be fine also...right now phone not booting up.. so i cant tell...
Understood, grabbing 4.42 Stock Images.
From this page: http://forum.xda-developers.com/showthread.php?t=2740496
I grabbed the first 2x Installers.
-KitKat 4.4.2. Stock Rom by robalm
-4.4.2 DN3 (Ditto Note 3) Rom from E-Team
Both are these are .zip files; the one by robalm suggests using Odin for install. The 2nd one by Electron Team using custom Recovery (CWM/TWRP).
Will try Electron Team first, and if nothing happens, will try Odin and 1st one.
tornado92 said:
There is no 5.0 stock firmware for n7100 . Latest is 4.4.2 if your phone model is n7100 in download mode. Then your phone isnt tmobile.. and about factory imei .. first unbrick your device to check the status of your imei.. it could be fine also...right now phone not booting up.. so i cant tell...
Click to expand...
Click to collapse
As u wish buddy. I recommend odin one first as its a stock firmware
Tried the Ditto Note3 ROM; no luck.
Inside TWRP Recovery, I did:
-Factory Reset
-Format Data
-inside Mount settings, verified EFS, cache, System, Data, Ext_SDCard were selected
-install Zip FAILED:
Error flashing zip ‘/external_sdcard/N7100XXUFND3_N7100OXAFND3_XEF.zip'
updating partition details…
…done
That is the extent of the error reporting. Tried 2x, both had same error log.
Yanked battery, went into Recovery again and re-installed the CM12 1007 Snapshot. I am back to the same loadscreen loop issue.
Moving on to Odin and the KitKat 4.4.2 ROM by robalm
motionmonk said:
Understood, grabbing 4.42 Stock Images.
Will try Electron Team first, and if nothing happens, will try Odin and 1st one.
Click to expand...
Click to collapse
Something happening with your partitions probably, listen the advice of tornado and flash it via odin.
Sent from my GT-N7100
Oh bugger me. Can't think straight.
I installed the wrong ROM. I copied the 'robalm' 4.4.2 KitKat ROM to my ext SD card by mistake. No wonder it failed.
Tried the correct DittoNote4 ROM; it failed.
This is from the TWRP recovery log:
minzip: Error writing 8192 bytes from zip file from 0xbe88da44: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/usr/srec/en-US/g2p_fst"
about to run program [/tmp/floating_message.sh] with 1 args
- Symlinking files
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sdcard/DN4_v2.1_by_E-Team.zip'
Error flashing zip '/external_sdcard/DN4_v2.1_by_E-Team.zip'
Updating partition details...
I: Data backup size is 6MB, free: 11168MB.
Still going to give the "robalm" ROM a try in Odin.
motionmonk said:
Tried the Ditto Note3 ROM; no luck.
Inside TWRP Recovery, I did:
-Factory Reset
-Format Data
-inside Mount settings, verified EFS, cache, System, Data, Ext_SDCard were selected
-install Zip FAILED:
Error flashing zip ‘/external_sdcard/N7100XXUFND3_N7100OXAFND3_XEF.zip'
updating partition details…
…done
That is the extent of the error reporting. Tried 2x, both had same error log.
Yanked battery, went into Recovery again and re-installed the CM12 1007 Snapshot. I am back to the same loadscreen loop issue.
Moving on to Odin and the KitKat 4.4.2 ROM by robalm
Click to expand...
Click to collapse
Heeehe guide line
1: must have a working brain hahahah buddy
YAY! I'm in!
I used N7105XXDMA6_Deodex_Rooted_01_28_13-teshxx.zip and flashed via TWRP Recovery.
I was able to enter Google info in Samsung setup, and am up on device desktop.
Insert SIM Card, check About Device, I have this for a Status Check...
Network-unknown
Mobile Network Type-unknown
Service State-Out of service
Roaming-not roaming
Mobile network state-disconnected
My phone number-Unknown
IMEI-Unknown
IMEISV-Unknown
At least it's not the Loadscreen is all I can say!
Ok, gone for a few for a late lunch.
Will let the device settle in, and will check back for any further suggestions.
Thanks again Tornado!
WOT?
Life has an... Operations Manual?
hehe
tornado92 said:
Heeehe guide line
1: must have a working brain hahahah buddy
Click to expand...
Click to collapse
Your not in buddy.. ur efs partition is probably screwed up whats the use of a phone if it doest detect sim :s
---------- Post added at 11:06 PM ---------- Previous post was at 11:04 PM ----------
Flash stock firmware via odin to check whether imei comes back or not.. and dont mess too much with phone.. imei repair is not a easy thing.. ahaahah my advice for u
---------- Post added at 11:12 PM ---------- Previous post was at 11:06 PM ----------
whats ur actual model number.. is it n7100 or n7105 .. if ur phone is n7100 dont use n7105 firmwares.. a both are different hardware wisely yet your imei corrupted now due to different modem in n7105 firmware...
Am still here, been trying to track down valid firmware images.
I believe my phone is a N7100. Somewhere in replacing ROMs in the past, I think I installed an Int'l N7105 TouchWiz ROM (Jedi-X) and stuck with that using a T-Mo modem file.
Found a stock 4.3 for my SGH-T889 T-Mobile GSM phone today. So, tried an install using JODIN, an open-source Odin app, but it didn't reboot the phone, so not sure if it took.
Going to install a Windows partition, load KIES and true ODIN and try again tomorrow. Will update then.
@motionmonk buddyy go to download mode(pres volume down +power+ home) and post screen shot of it..
Sent from my GT-N7105 using Tapatalk
i747 Galaxy S3 only boots into download mode, Odin Stuck on "Initialization"
Hey guys, so I finally decided to post here after spending an embarrassing amount of time trying to fix my problem and getting nowhere. I have an i747 Samsung Galaxy S3 that gets stuck on the loading screen when booting, and won't go into recovery mode (download mode works fine). I have tried to flash the original 4.3 firmware using Odin with no success...it keeps getting stuck on the "Initialization" step. I've tried 3 different cables, 2 different laptops with 5 usb ports in total, 3 different versions of Odin (3.07, 3.09, 3.10) all to no avail. I have downloaded the Samsung Mobile Drivers and my computer does recognize the device (though it thinks its a modem and not a phone). I'd appreciate some assistance in reviving my device, thanks!
Might be important so i'll mention it. I cannot remember the most recent firmware that the phone was displaying before it died, it might have been 4.1 or 4.2 but I read somewhere else that if it says "Warranty Bit" in download mode that implies it is 4.3?
I've also tried using two different md5 files, one from http://androidromupdate.com/att-samsung-galaxy-s3-sgh-i747-odin-stock-firmware/ and the other from http://forum.xda-developers.com/showthread.php?t=2722660&page=5
In download mode, my phone displays this:
Odin Mode
Product Name: SGH-I747
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Warranty Bit: 0
BOOTLOADER RP SWREV: 2
Since your phone is the i747, there is not stock firmware that can be flashed with Odin that is newer than 4.1.1. All updates for the i747 were released via OTA updates.
I suggest verifying the bootloader and modem on your phone before flashing anything else as an incompatible bootloader and modem combination can hard brick the phone.
To get the phone booted, I would flash TWRP for the d2lte via Odin and then flash a custom ROM such as cm12.1. Once booted you can veriify the bootloader and modemr and modem.
audit13 said:
Since your phone is the i747, there is not stock firmware that can be flashed with Odin that is newer than 4.1.1. All updates for the i747 were released via OTA updates.
I suggest verifying the bootloader and modem on your phone before flashing anything else as an incompatible bootloader and modem combination can hard brick the phone.
To get the phone booted, I would flash TWRP for the d2lte via Odin and then flash a custom ROM such as cm12.1. Once booted you can veriify the bootloader and modemr and modem.
Click to expand...
Click to collapse
Interesting. How do I verify the bootloader and modem on the phone? Does the information provided in download mode tell me this? I have no way of booting up the phone to check its settings.
Also regarding OTA, do you think this guide would work for me? http://forum.xda-developers.com/showthread.php?t=2549068
Your phone is not bricked so I would not use that thread.
Download the latest tar version of twrp for the d2lte (AT&T version of s3) from here: https://dl.twrp.me/d2att/
Download the latest CM11 from here: http://download.cyanogenmod.org/?device=d2lte
Download the 4.4 Gapps package for ARM from here: http://opengapps.org/?api=4.4&variant=nano
Download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=...168421&usg=AFQjCNEdxqAS5QWImOPDJboTA_V3D5S9eA
Boot the phone into download mode, open Odin 3.07, uncheck everything except f.reset time. Flash TWRP in the PDA slot. When you see the word "reset" in the status window, remove the USB cable from the phone remove the battery, wait 5 seconds, replace the battery, boot the phone into recovery mode using the home, power, and volume up button. When the phone boots to recovery mode, you should see the TWRP recovery.
With the phone in TWRP, connect the phone to the computer, copy cm11 and Gapps to the phone's internal storage.
Within TWRP, wipe the system, cache, data, install cm11, install gapps, reboot.
audit13 said:
Your phone is not bricked so I would not use that thread.
Download the latest tar version of twrp for the d2lte (AT&T version of s3) from here: https://dl.twrp.me/d2att/
Download the latest CM11 from here: http://download.cyanogenmod.org/?device=d2lte
Download the 4.4 Gapps package for ARM from here: http://opengapps.org/?api=4.4&variant=nano
Download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=...168421&usg=AFQjCNEdxqAS5QWImOPDJboTA_V3D5S9eA
Boot the phone into download mode, open Odin 3.07, uncheck everything except f.reset time. Flash TWRP in the PDA slot. When you see the word "reset" in the status window, remove the USB cable from the phone remove the battery, wait 5 seconds, replace the battery, boot the phone into recovery mode using the home, power, and volume up button. When the phone boots to recovery mode, you should see the TWRP recovery.
With the phone in TWRP, connect the phone to the computer, copy cm11 and Gapps to the phone's internal storage.
Within TWRP, wipe the system, cache, data, install cm11, install gapps, reboot.
Click to expand...
Click to collapse
Thanks, i'll definitely be trying this!
Just to make sure i'm following the steps correctly, by latest CM11 is that the latest release, or latest release recovery? And for the the 4.4 Gapps package for ARM, i'm not sure which option to select under "variant". It is on nano by default, should I select stock?
audit13 said:
Your phone is not bricked so I would not use that thread.
Download the latest tar version of twrp for the d2lte (AT&T version of s3) from here: https://dl.twrp.me/d2att/
Download the latest CM11 from here: http://download.cyanogenmod.org/?device=d2lte
Download the 4.4 Gapps package for ARM from here: http://opengapps.org/?api=4.4&variant=nano
Download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=...168421&usg=AFQjCNEdxqAS5QWImOPDJboTA_V3D5S9eA
Boot the phone into download mode, open Odin 3.07, uncheck everything except f.reset time. Flash TWRP in the PDA slot. When you see the word "reset" in the status window, remove the USB cable from the phone remove the battery, wait 5 seconds, replace the battery, boot the phone into recovery mode using the home, power, and volume up button. When the phone boots to recovery mode, you should see the TWRP recovery.
With the phone in TWRP, connect the phone to the computer, copy cm11 and Gapps to the phone's internal storage.
Within TWRP, wipe the system, cache, data, install cm11, install gapps, reboot.
Click to expand...
Click to collapse
I tried that too, but I get status 7 and 0 in recovery. I've tried cm 13.1-cm 11..ugh when I try to wipe cache, it gets stuck. I hear when that happens I have a soft brick. What should I do?
Did you get twrp on the phone? Maybe try version 2.8.7.
Tried old cwm, twrp 3.0 and twrp 2.8
---------- Post added at 06:24 PM ---------- Previous post was at 06:23 PM ----------
audit13 said:
Did you get twrp on the phone? Maybe try version 2.8.7.
Click to expand...
Click to collapse
Yes. I was able to flash a recovery.
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
I flashed d2att tar recovery
---------- Post added at 06:29 PM ---------- Previous post was at 06:26 PM ----------
audit13 said:
Did you get twrp on the phone? Maybe try version 2.8.7.
Click to expand...
Click to collapse
What do I do if that's successful?
Tmobilefan906 said:
Tried old cwm, twrp 3.0 and twrp 2.8
---------- Post added at 06:24 PM ---------- Previous post was at 06:23 PM ----------
Yes. I was able to flash a recovery.
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
I flashed d2att tar recovery
---------- Post added at 06:29 PM ---------- Previous post was at 06:26 PM ----------
What do I do if that's successful?
Click to expand...
Click to collapse
Thanks for hijacking my thread, lol. Could you at least answer these questions for me?
by latest CM11 is that the latest release, or latest release recovery? And for the the 4.4 Gapps package for ARM, i'm not sure which option to select under "variant". It is on nano by default, should I select stock?
Flash a custom rom from recovery to get the phone booted.
DemolitionX said:
Thanks for hijacking my thread, lol. Could you at least answer these questions for me?
by latest CM11 is that the latest release, or latest release recovery? And for the the 4.4 Gapps package for ARM, i'm not sure which option to select under "variant". It is on nano by default, should I select stock?
Click to expand...
Click to collapse
I'm having same issues as u. Rather hijack than create a new one. Lol
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
DemolitionX said:
Thanks for hijacking my thread, lol. Could you at least answer these questions for me?
by latest CM11 is that the latest release, or latest release recovery? And for the the 4.4 Gapps package for ARM, i'm not sure which option to select under "variant". It is on nano by default, should I select stock?
Click to expand...
Click to collapse
Yea...latest one...and nano
Now its stuck at nand start..UGGGGH
audit13 said:
Did you get twrp on the phone? Maybe try version 2.8.7.
Click to expand...
Click to collapse
Hey audit. When I tried downloading the latest twrp as you suggested, after extracting the file i'm only left with a recovery.img file. When using Odin and selecting PDA, it doesn't recognize the .img file and so I can't select it. I thought I need a tarmd5 file to flash with odin? Please advise me on how to proceed, thanks. (Btw, i tried downloading both the twrp-3.0.2-0-d2att.img.tar and the twrp-3.0.2-0-d2att.img, they both gave me recovery.img files when extracted).
Also I have another question, could you point me in the direction of a data cable that is 100% Odin approved? I'd really like to eliminate the possibility of a non-effective data cable preventing Odin from working properly.
audit13 said:
Flash a custom rom from recovery to get the phone booted.
Click to expand...
Click to collapse
Was and is t999l coming with a locked bootloader?
Don't extract the twrp tar file, just flash it in Odin.
T999L should not have a locked bootloader.
audit13 said:
Don't extract the twrp tar file, just flash it in Odin.
T999L should not have a locked bootloader.
Click to expand...
Click to collapse
OK. Cuz I got a mobo to put into the i747 frame. And I want it rooted. Thanks again.
audit13 said:
Don't extract the twrp tar file, just flash it in Odin.
T999L should not have a locked bootloader.
Click to expand...
Click to collapse
When I put this in the PDA slot and click start, it just gets stuck on initialization again. No matter what I try and flash it just gets stuck on the initialization step...
Based on the threads below, it seems I have a hardware problem and will need to replace the motherboard. *sigh*
http://forum.xda-developers.com/galaxy-s4/help/odin-stuck-initialization-step-t2965693/page2
http://forum.xda-developers.com/galaxy-s4-mini/help/able-to-load-via-download-mode-odin-gt-t3040253
You're using the original Samsung USB cable? Tried different usb ports? Tried different versions of Odin and windows?
audit13 said:
Your phone is not bricked so I would not use that thread.
Download the latest tar version of twrp for the d2lte (AT&T version of s3) from here: https://dl.twrp.me/d2att/
Download the latest CM11 from here: http://download.cyanogenmod.org/?device=d2lte
Download the 4.4 Gapps package for ARM from here: http://opengapps.org/?api=4.4&variant=nano
Download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=...168421&usg=AFQjCNEdxqAS5QWImOPDJboTA_V3D5S9eA
Boot the phone into download mode, open Odin 3.07, uncheck everything except f.reset time. Flash TWRP in the PDA slot. When you see the word "reset" in the status window, remove the USB cable from the phone remove the battery, wait 5 seconds, replace the battery, boot the phone into recovery mode using the home, power, and volume up button. When the phone boots to recovery mode, you should see the TWRP recovery.
With the phone in TWRP, connect the phone to the computer, copy cm11 and Gapps to the phone's internal storage.
Within TWRP, wipe the system, cache, data, install cm11, install gapps, reboot.
Click to expand...
Click to collapse
Whew. Your post just saved my bacon. I was stuck at a never ending odin mode loop after installing TWRP via the TWRP app. Freaked out a bit. Used Odin via your instructions and got TWRP loaded and working. Thanks alot, appreciate the help.
jdlucid said:
Whew. Your post just saved my bacon. I was stuck at a never ending odin mode loop after installing TWRP via the TWRP app. Freaked out a bit. Used Odin via your instructions and got TWRP loaded and working. Thanks alot, appreciate the help.
Click to expand...
Click to collapse
Glad my method worked for you :good:
All,
Tried to root Verizon Note 4 following instructions on this site: galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4
After getting root I got to the point where I flashed the system-only ROM and Odin reported success. On reboot with TWRP that it got stuck in boot loop.
Downloaded full firmware ROM and flashed it in the hopes of starting from scratch and now TWRP is gone and it's still stuck in boot loop.
Factory wipe didn't work. Up-vol - Home - Power displays the factory recover screen.
Any ideas on how to get it back to factory or some other working firmware?
-Thx
SOLVED
Found a factory ROM for the N910V and upgraded Odin to latest version. Started in download mode, flashed ROM with Odin, all is well. I think I had a corrupted ROM that didn't flash.
Now that I've recovered this thing successfully I'll have another go at rooting it so I can get rid of the bloat for good. I'll probably be back with another tale of misery after bricking it...
spumco said:
All,
Tried to root Verizon Note 4 following instructions on this site: galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4
After getting root I got to the point where I flashed the system-only ROM and Odin reported success. On reboot with TWRP that it got stuck in boot loop.
Downloaded full firmware ROM and flashed it in the hopes of starting from scratch and now TWRP is gone and it's still stuck in boot loop.
Factory wipe didn't work. Up-vol - Home - Power displays the factory recover screen.
Any ideas on how to get it back to factory or some other working firmware?
-Thx
Click to expand...
Click to collapse
Are you still stuck?
Sort-of. I found a clean factory MM ROM that fixed everything and the phone is live and happy. ROM N910VVRU2CPG2.
However, I'm unable to root it now. Searched a number of threads and have not been able to find a KingOroot or TWRP that will work. Nor can I downgrade to 5.1.1 and start from there.
So working phone, but no root and all bloatware intact. If you (or anyone else) has a idiot-friendly solution I'm all ears.
spumco said:
Sort-of. I found a clean factory MM ROM that fixed everything and the phone is live and happy. ROM N910VVRU2CPG2.
However, I'm unable to root it now. Searched a number of threads and have not been able to find a KingOroot or TWRP that will work. Nor can I downgrade to 5.1.1 and start from there.
So working phone, but no root and all bloatware intact. If you (or anyone else) has a idiot-friendly solution I'm all ears.
Click to expand...
Click to collapse
It wont't let you downgrade? Had you pulled the sd card?
---------- Post added at 03:01 PM ---------- Previous post was at 02:50 PM ----------
What happens when you flash 5.1.1?
ziggy71 said:
It wont't let you downgrade? Had you pulled the sd card?
---------- Post added at 03:01 PM ---------- Previous post was at 02:50 PM ----------
What happens when you flash 5.1.1?
Click to expand...
Click to collapse
Doesn't matter what version ROM, Odin now fails to write. And I cant get Kingoroot to do the temp root, so doing the Console/ADB trick right after temp root doesn't work.
PC version of Kingoroot doesn't work either.
I'm sure there's a way to break in to this thing, but I'm such a novice it's not even funny.
Well the exploit is in 5.1.1. So that is what you need to be on. Try a different version of odin, try a factory reset on the phone
https://androidfilehost.com/?fid=24411628330026105
That's the full 5.1.1. Install that and get your phone going. If you can't get that installed, then you can't root
ziggy71 said:
Well the exploit is in 5.1.1. So that is what you need to be on. Try a different version of odin, try a factory reset on the phone
https://androidfilehost.com/?fid=24411628330026105
That's the full 5.1.1. Install that and get your phone going. If you can't get that installed, then you can't root
Click to expand...
Click to collapse
Thanks much. I'll D/L it and have a go. Will report back either way.
SUCCESS!
The full 5.1.1 install was successfully loaded. I then followed the root exploit found on this forum (I think it was the 'simplified' thread) and Kingroot worked the 2nd try. The cleaned up stock ROM linked in the rooting thread was also loaded, along with TWRP.
Thanks a ton for the assistance!
Glad it worked out for you.