I have first mentioned the problem here
Discussion - Stuck at Sammy Logo Issue on Official Jellybean ROMs
Mates, the problem is there, we should admit that, had it on Galactus rom twice ( reflashed the rom again after full wipes to make sure ), and had it also on the stock LSZ with its stock kernel, and also on Cassie's rom.
Nothing solves the problem apart from wiping data.
Is it the preload ? the kernel ? defective JB from Samsung ? I really don't know.
The only thing I would really like to mention is that on Stock and Cassie's rom, had the issue surprisingly occuring on odd restarts not the even ones ! the first restart gets stuck, the other goes on !
Tried all the tricks in the book (restart to recovery, reinstalling bootloader, overinstalling the same rom, wiping everything keeping data, nothing worked.
Unless data gets wiped, the problem persists.
BTW, I had the same problem on all the previous leaked versions before the official ones.
Click to expand...
Click to collapse
The method was first described here and here by RbbCHan
Then suggested to me by kopitalk
Hi mate, finally I resolved this issue by following http://forum.xda-developers.com/show...postcount=2344 and http://forum.xda-developers.com/show...postcount=2347.
Now no matter I hard reset or reboot from recovery, I got no boot stuck anymore! Cheers mate!!!
Click to expand...
Click to collapse
So here is what I have done " a step by step guide"
1-on a safe kernel, do all wipes+formats 9system,data, and preload".
2-reboot into DOWNLOAD mode.
3-connect your N7000 to PC (I use PC Odin V. 3.04).
4-start PC ODIN, untic "Automatic Reboot"
5-flash stock official LSZ rom
6-when you see the word "PASS", restart into DOWNLOAD MODE ( holding vol down+home+power).
7-reflash again.
8-when you see the word "PASS", restart into DOWNLOAD MODE ( holding vol down+home+power).
8-reflash again (3rd time)
9-restart you phone.
10-let the rom settle down, do your settings.
11-do a couple of restarts (legitimate ones, not by holding power for 7secs).
12-root your rom with the latest PhilZ LSZ kernel
13-restart into recovery, format data only "under mount and storage", then restart your phone.
Installed eybee's rom with mods, restarted automatically after mod3, and right now I am with a JB rom that does not stuck at sammy logo even when I force restart pressing the power button for 7 sec.
If you feel it takes a longer time on Sammy N7000 Logo, just repress power button again for 7 secs and it will boot up.
Hope this helps anyone who suffered bootloops as I did.
Have you taken out the battery while Note was on? That's what causing bootloops, just rebooting not necessarily.
Will try and report...:fingers-crossed::fingers-crossed:
---------- Post added at 01:32 PM ---------- Previous post was at 01:28 PM ----------
on 13rd steep should I wipe data/factory reset or format data under mount and storage?
zai89 said:
Will try and report...:fingers-crossed::fingers-crossed:
---------- Post added at 01:32 PM ---------- Previous post was at 01:28 PM ----------
on 13rd steep should I wipe data/factory reset or format data under mount and storage?
Click to expand...
Click to collapse
mount and storage mate..
the JB bootloader will help and are they missing in ur step?
arinsms said:
the JB bootloader will help and are they missing in ur step?
Click to expand...
Click to collapse
its in step 5 - the official rom has the JB bootloader sbi.bin
though I'm crossing fingers that this will work for everyone, but i doubt....this is completely weird from any logical point of view (especially these 3 flashes in a row...what will be flashed on 2nd or 3rd attempt that wasn't flashed before??)...but hey...if it works, ok
Your forgot step 14: turn around yourself 3 times spitting every turn in your preferred direction.
Sorry but I have to ask: is this still a developer forum with a technical/scientifical approach for problems and solutions?
Superstition reigns...
AW: N7000 Official JB Bootloop - "3x Bombardment Odin Flash" simply works!!
If I would have the bootloop problem (actually I never faced any) I would definitely give this a try. Superstition or not, doesn't matter if it solces the problem, right?
Sent from my GT-N7000 using xda premium
ThaiDai said:
Your forgot step 14: turn around yourself 3 times spitting every turn in your preferred direction.
Sorry but I have to ask: is this still a developer forum with a technical/scientifical approach for problems and solutions?
Superstition reigns...
Click to expand...
Click to collapse
This is really silly of you. We are all trying to figure out a solution even if a temporary one which might help hundreds if not thousands who are trying to use their phones promptly and who regret buying this n7000 with the famous ics brick bug and now the unstable jb roms which are OFFICIAL SAMSUMG RELEASES.
To all, there really should be a 'counter' somewhere, which explains the 'every other restart' that succeeds and does not cause the n7000 to get stuck.
Sent from my GT-N7000 using Tapatalk 2
essentially we are just ensuring the new image sticks
coz there may not be a way to verify which bootloader we actually have even after first flash
ThaiDai said:
Your forgot step 14: turn around yourself 3 times spitting every turn in your preferred direction.
Sorry but I have to ask: is this still a developer forum with a technical/scientifical approach for problems and solutions?
Superstition reigns...
Click to expand...
Click to collapse
Shame on you... We may not know what's behind doing it but it works. I hope you will get this broplem so that you will swallow your saliva back.
I'm not ashamed and I do not feel silly because of my statement.
It's only my point of view and so I still think this is ridiculous.
If any member is positive about the results my comments never will change it.
But that won't stop me from commenting when rationality moves to the far side of the moon.
I don't know if it works; installing the bootloader seems to work too to avoid soft reboot bootloops. But when I take out the battery while the Note is on I get the bootloop.
J, have you taken out the battery to test if it works? That's what I'm interested in right now.
Why does anyone take there battery out while the phone is on!? Can one magically change the batteries without switching off the phone?
dio62000 said:
I don't know if it works; installing the bootloader seems to work too to avoid soft reboot bootloops. But when I take out the battery while the Note is on I get the bootloop.
J, have you taken out the battery to test if it works? That's what I'm interested in right now.
Click to expand...
Click to collapse
Ues, I have just done that replacing my stock battery with my 5000mAh, and it has worked just fine.
Sent from my GT-N7000 using Tapatalk 2
Sometimes you need to take your battery out, e.g. when you have a crash and nothing responds to buttons or touch anymore. I won´t happen too often, but once is enough to get really annoyed, because this always happens when you least expect it.
dio62000 said:
I don't know if it works; installing the bootloader seems to work too to avoid soft reboot bootloops. But when I take out the battery while the Note is on I get the bootloop.
J, have you taken out the battery to test if it works? That's what I'm interested in right now.
Click to expand...
Click to collapse
Yes, I have just done that replacing my stock battery with my 5000mAh and it has worked just fine.
Sent from my GT-N7000 using Tapatalk 2
Ok, so you didn´t first shut off the phone, you took out the battery while it was still on? Now that may be interesting...
dio62000 said:
Sometimes you need to take your battery out, e.g. when you have a crash and nothing responds to buttons or touch anymore. I won´t happen too often, but once is enough to get really annoyed, because this always happens when you least expect it.
Click to expand...
Click to collapse
If a system freeze occurs, you don't have to pull the battery. You can long-press the power button and voila, reboob™ takes place!
How do you guys call this... soft reboot, soft reset...?
Related
I think I found out the cause of some bootloopings and its the "Log Switch" option in project menu.
When we try to root the rom and the the phone reboots:
A)if he reboots ok, you must go again into project menu (*#*#2846579#*#*) and "switch off" the Log.
Everyone tell us we must switch this thing on in order to root the phone but no one says that we should turn it off again after proccess completed....
B) if starts immediatly with bootlooping and never booted againd after the rooting proccess just take the battery out andenter into recovery (vol up + Power). Once there make a "Data factory reset" and reboot.
The phone will then start normally this time with no Bootloopings.
With luck you have SU installed and the phone is rooted.
If yes, just go to project menu (*#*#2846579#*#*) and "switch off" the Log.
If not just try the rooting again
But the major deal is the Log Switch.
Hope it helps anyone
I never had bootloops with 2.3 official rooted and log switch was turned on before and after
I'm happy for you!
Moved to General
Thought this may be helpful to some, it has no place in the development section.
Thanks for the contribution, i would usually close, but as it could be helpful, on this occasion i will move it.
Take it easy
O_G
yes don't close it please as I noticed that many had bootloop issues with these releases. I was one of them but this finished after switching the log of. In my caes that solved my problems.
I had thought that too but none of the combinations i tried worked.
I had tried switching off Logging,factory data reset,flashed again without rooting and after 2-3 days that everything seemed that worked normal and i had loaded all apps i wanted, bootloop appeared again and had to factory data reset again in order to use phone.
So i gave up and reverted to 2.2
I never had bootloops but if that's really what's causing it, that's a great catch!
Congrats!
well as I said with me, since I have done this the bootlooping stoped.
Before Everytime I reboot the bootlooping started and only stoped with a factory reset. Then I tried to switch Log Off again and not a single bootloop and more than 48 hours.
Flashed OC kernel, UOT Kitchen, etc etc and phone running perfect.
Look, I have flashed and tested this rom many many many times and alwas endup with bootlooping eventually. This did the trick for me and I consider it a major step as I can now use the rom freely and without being afraid.
As I said, is just 1 more Idea that people having this issue could try out and see if helps.
I just took the liberty of sharing this so that in case o dispair for some, they can have other alternatives.
Didn't help me, actually it did the opposite...my phone didn't boot loop until I went and touched the freaking "Log switch" option...should have let it ON...GRRRR....Got to taste Huawei's bad medicine again...or my own...I should have known; if it ain't broken, don't try to fix it!
lololol
Huawei's each one with own personality...
Druida69 said:
lololol
Huawei's each one with own personality...
Click to expand...
Click to collapse
Indeed!
Mine, for example, had precisely the opposite behaviour.
In order to root the phone, with the latest official GB ROM, i had to switch the logging to On. Otherwise i got bootloop with every ROM. I was also unable to root the official roms without logging On.
Well, at least it was coherent.
Question: When we flash a new ROM the logging is turned off by default, right?
If so, how can it influence negatively the ROM stability?
Druida69 said:
lololol
Huawei's each one with own personality...
Click to expand...
Click to collapse
Tell me about it.
SilveRRing said:
Indeed!
Mine, for example, had precisely the opposite behaviour.
In order to root the phone, with the latest official GB ROM, i had to switch the logging to On. Otherwise i got bootloop with every ROM. I was also unable to root the official roms without logging On.
Well, at least it was coherent.
Question: When we flash a new ROM the logging is turned off by default, right?
If so, how can it influence negatively the ROM stability?
Click to expand...
Click to collapse
You understand it opposite m8.
You must turn the Lon On to root the phone.
After root my advice is to turn it back Off again as it was from the beginning..
Ah ok, nevermind then. lol
my x5 dont have bootloop but this topic will help very people,thanks for the trick lol
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
driuda you have a theme of UOT Kitchen??? I make one for me but failed,please help me?i dislike stock theme is for children hehehe
at the moment I only used UOT this time to change the battery icon to battery percentage circular.
Its one of those must haves that I miss from official rom, the battery percentage....
Coking a theme is very easy. You just choose all the option you want and in the end upload the framework-res.apk and SystemUI.apk files and wait for the coking.
After that pick up the file and flash it with CWM.
mhh i dont think that the log switch is the only thing that causes bootloops.
first i installed 2.3.5 and a few hours later i switched the og on. The bootloops started.
So i had to do a factory reset...
Now after the reset I quikly turned off the log switch. but just a few hours later it started again bootlooping......
any other ideas? or do i have to go back to miui? when yes can i do the following?
: 1. factory reset
2. get root
3. install cwm
4. install my backup?
let me see if I understand.
You installed the latest official release, then you switch the log on? for what?
I assume you switch it on to root. Did you root it?
Yes yes you did well by turn it off as the log is off by default.
Next step should be installing the CWM 5.0.2.7.
Unfortunatly after bootlooping start only solution is factory reset which means having the phone all wiped again which is a pain after a few hours of putting it at our taste.
I think restoring a MIUI backup through CWM won't work.
I have tried this preocedure several times with MIUI or any other custom rom.
The correct way to go gack is downgrading to an official 2.2 release, then root it, install CWM, install a MIUI rom (in your case) doing all the 3 wipes. After you confirm that the rom was installed correctly and is working you can then go to CWM and restore a backup.
Druida69 said:
let me see if I understand.
You installed the latest official release, then you switch the log on? for what?
I assume you switch it on to root. Did you root it?
Yes yes you did well by turn it off as the log is off by default.
Next step should be installing the CWM 5.0.2.7.
Unfortunatly after bootlooping start only solution is factory reset which means having the phone all wiped again which is a pain after a few hours of putting it at our taste.
I think restoring a MIUI backup through CWM won't work.
I have tried this preocedure several times with MIUI or any other custom rom.
The correct way to go gack is downgrading to an official 2.2 release, then root it, install CWM, install a MIUI rom (in your case) doing all the 3 wipes. After you confirm that the rom was installed correctly and is working you can then go to CWM and restore a backup.
Click to expand...
Click to collapse
yes i did turn it on becuase i wawnted to prepare it for rooting but since im not at home since 3 days i cant.
But after the bootlooping i turned it off, but it bootlooped later again....
thank you for the intriductions!
edit: where can i find the 2.2 stock rom for germany? and how to install it? like 2.3.5?
levibuko said:
yes i did turn it on becuase i wawnted to prepare it for rooting but since im not at home since 3 days i cant.
But after the bootlooping i turned it off, but it bootlooped later again....
thank you for the intriductions!
edit: where can i find the 2.2 stock rom for germany? and how to install it? like 2.3.5?
Click to expand...
Click to collapse
if it is to downgrade and then move forward to any other rom, custom or not, you can use any version don't loock spexifically to a german one.
Here you have a list of stock rom:
http://forum.xda-developers.com/showthread.php?t=1167882
http://wiki.modaco.com/index.php/Huawei_Firmware_U8800 (MOdaco Wiki)
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8800_IDEOS_X5 (XDA Wiki)
I have updated to ICS via OTA.
Now, if i open keypad to dial it first shows grey screen for 2seconds and then the numbers appears... Same with contacts.
I also got couple of times black screen as if phone frooze.
Once, even i got scrambled green images on screen which got corrected by pressing Home button multiple times.
Apart from this, Phone seems to be running fine.
So, how can i myself solve this problem now OR Do i have to go to Samsung service centre and let them reinstall ICS?
PS:
I am using Indian official ICS Baseband Ver. LP4 & Build Number LP8.
I have never rooted and was on Stock GB before the urgrade.
I fear if i try to fix this ICS problem myself i will run into bricking problem.
UPDATE
See post 7 & 13 Below
I had this issue but after i wired data using code *2767*3855# everything worked smoothly.
You can try this at your own risk as it might brick if yor device has emmc bug. I have already done it over 15 times and no issue
Sent from my GT-N7000 using XDA
olivespin said:
I have updated to ICS via OTA.
Now, if i open keypad to dial it first shows grey screen for 2seconds and then the numbers appears... Same with contacts.
I also got couple of times black screen as if phone frooze.
Once, even i got scrambled green images on screen which got corrected by pressing Home button multiple times.
Apart from this, Phone seems to be running fine.
So, how can i myself solve this problem now OR Do i have to go to Samsung service centre and let them reinstall ICS?
PS:
I am using Indian official ICS Baseband Ver. LP4 & Build Number LP8.
I have never rooted and was on Stock GB before the urgrade.
I fear if i try to fix this ICS problem myself i will run into bricking problem.
Click to expand...
Click to collapse
I rooted my Note after about two days so not sure if this will work on non-root....
Reboot into recovery (Power+Vol Up + Home) then clear cache and clear Dalvik cache. Reboot then see if lag continues. Clearing caches and reboot seems to get rid of lags and gives phone a new life
Today again phone got frooze on homescreen for 5mins and got back to life again after pressing Home key numerous times
So yes, something is wrong with this ICS update.
Plz provide a solution and also mention if tht solution can lead to bricking bug..
BUMP.
I had exactly the same problems while updating Gb to ICS using OTA update. Anywhow, I never got to fix this. I would try following steps:
Clean the cache of your ICS installations/apps using any Cache-cleaning tool on the Play Store
Reboot your phone like 2-3 times (sometimes this seems to fix some problems with your kernel/rom since they have to settle down.
Update all your apps to their latest versions, since most apps have fixes for ICS installations, and might slow your phone a bit down in some way
Click to expand...
Click to collapse
When you still would have problems with your ICS installations I would recommend installing a custom rom over your stock ICS installation. This did the trick for me eventually.. But depends on if you would like to have a stock or custom ICS rom.
HELP
I tried the above suggestion and done Factory Format via *2767*3855#.
Now, after entering code the device havent rebooted for the next 15mins, so i pressed the power key to reboot manually and then i got the message format failed or sumthing similar which i dont seem 2 recall.
Now, all my Smemo data & camera images is wiped... but phone numbers and messages intact.
and the originally mentioned problem is still there..... So wht is my solution now ?
I want to delete every old system files & Clean-install ICS - So Is it via kies?
Dont know much abt all this so a detailed help would be highly appreciated.
olivespin said:
I have updated to ICS via OTA.
Now, if i open keypad to dial it first shows grey screen for 2seconds and then the numbers appears... Same with contacts.
I also got couple of times black screen as if phone frooze.
Once, even i got scrambled green images on screen which got corrected by pressing Home button multiple times.
Apart from this, Phone seems to be running fine.
So, how can i myself solve this problem now OR Do i have to go to Samsung service centre and let them reinstall ICS?
PS:
I am using Indian official ICS Baseband Ver. LP4 & Build Number LP8.
I have never rooted and was on Stock GB before the urgrade.
I fear if i try to fix this ICS problem myself i will run into bricking problem.
Click to expand...
Click to collapse
Facing the EXACTLY the same problem man.. Feel i have done a mistake by upgrading to ics
Sent from my GT-N7000 using xda premium
androidlover1 said:
Facing the EXACTLY the same problem man.. Feel i have done a mistake by upgrading to ics
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Somebody give us proper solution to this.. HELP!
Sent from my GT-N7000 using xda premium
Flash gingerbread again with odin, then do a factory reset... then upgrade to ics again using odin...
I dont want to go to GB again..... All i want is fresh clean install of ICS on my phone... So how to do tht ? (i dont wana play with my phones warrenty)
You can use pc odin to flash stock ics, not recommended though as you're on ics kernel now. Best to follow previous poster, fladh gb stock kernel first.
please hit thanks if i helped
SpyderTracks said:
You can use pc odin to flash stock ics, not recommended though as you're on ics kernel now. Best to follow previous poster, fladh gb stock kernel first.
Click to expand...
Click to collapse
If i use odin to flag GB first, will i loose my phones warrenty? (And i dont even knw how 2 use it)
Second, can i go 2 samsung service centre and let them delete all old files and install fresh copy of ICS? If i do, will i run a chance of bricking..... Coz i dont want to run into parts replacements and repairs problem...
What is the best solution now.
olivespin said:
If i use odin to flag GB first, will i loose my phones warrenty? (And i dont even knw how 2 use it)
Second, can i go 2 samsung service centre and let them delete all old files and install fresh copy of ICS? If i do, will i run a chance of bricking..... Coz i dont want to run into parts replacements and repairs problem...
What is the best solution now.
Click to expand...
Click to collapse
Since you did nothing wrong that could void your warranty, and you don't know too much about fixing it yourself, save yourself the hassle and let a Service center take cre of it for you .
Hey guys,
this is my first post and my problem is as follows:
I had ICS 4.0.x on my galaxy tab 10,1 P7500, I then installed CWM 5.5.0.4. but had a rolling window. I then continued to install a bootloader (here: http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41) with the appropriate bootloader for the p4. This fixed the rolling recovery and allowed me to install CM10 using CWM.
But my current problem is when the device goes on sleep mode and I wake the device up the screen is scrambled, can anyone tell me how to fix this?
Thank you in advance
The only fix i found is for HC
http://forum.xda-developers.com/showthread.php?t=1680738
Edit:
I fixed the rolling screen issue after screen unlock with pershoot's help, thanks again pershoot!
Maybe it will also work for you , here we go:
If you have installed the latest cm10 build, there is only one issue for the p4wifi , you must be on the US ICS Bootloader .
So download the recovery.tar.md5 from here:
http://droidbasement.com/galaxy/roms/cm10/p4wifi/recovery.tar.md5
Than go into download mode and flash this recovery using ODIN, (select pda and look for this file where you safed it, than click start)
Than, download the right US ICS Bootloader here:
http://droidbasement.com/galaxy/roms/cm10/p4wifi/US_LPL_4.0.4_bootloader.zip
Flash this also via ODIN in the PDA section, this may take a little longer, don't panic...
After that, the tablet will reboot and it should work... don't blame me if it didn't, but i had this rolling screen on almost every rom, and everything is fixed now...
I wish you good luck because i know it IS very annoying..
Thanks for the reply DefQon, I agree I think this is most annoying errors I have ever gotten.
I also searched high and low and could only find the fix for HC.
DefQoN_BE said:
I have EXACT the same issue, i'm running the latest cm10 build from droidbasement.com, if anyone can please help us???
The only fix i found is for HC
http://forum.xda-developers.com/showthread.php?t=1680738
I wish you good luck because i know it IS very annoying..
Click to expand...
Click to collapse
I have tried this method and works perfectly!
Thank you sooo much!!!
I am afraid to put a rom on my 10.1, i love it though!
blacks10 said:
I am afraid to put a rom on my 10.1, i love it though!
Click to expand...
Click to collapse
There's nothing you should be afraid of there is a fix for everything, and if you can't find it? There are nice poeple out there who wants to solve your problrm on xda developers forum
@drefcom: you're welcome
Please help - When turning off the Screen Android 4.1.1 will not come back on
I have the following problem.
When I install one of the latest rom e.g.
[ROM] [JB] [P4--P4WIFI--P4VZW]
4.1.2 AOKP for the Galaxy Tab 10.1
or
[ROM][JB][CM10] Android 4.1.1 - CyanogenMod 10 Preview
then I have this problem:
When I turn off with the "Power"-Hardbutton, then it turns off, but it does not turn back on. The screen stays black.
With the Rom ...
[ROM][JB][CM10] Android 4.1.1 - CyanogenMod 10 Preview "cm-10-20120814-EXPERIMENTAL-p4.zip" from August everything works fine.
Since I had this flickering problem I flashed the bootloader before I installed all these Roms.
But one works and all new ones don't.
Anyone has a idea what to do?
thx
drefcom said:
Thanks for the reply DefQon, I agree I think this is most annoying errors I have ever gotten.
I also searched high and low and could only find the fix for HC.
I have tried this method and works perfectly!
Thank you sooo much!!!
Click to expand...
Click to collapse
:good:
Thanks this helped me fix a mates Galaxy Tab 10.1
I was starting to pull my hair out and this worked so well.
Takes no time to do and no need to reflash the rom.
Hi guys.
speersie said:
:good:
Thanks this helped me fix a mates Galaxy Tab 10.1
I was starting to pull my hair out and this worked so well.
Takes no time to do and no need to reflash the rom.
Click to expand...
Click to collapse
i tried this method, but at second flashing (bootloader.zip) i get "0 succeed/0 failed" and still i get that scramble, and have to reboot all the time.
Any ideas?
Thanks in advance.
Cheers!:good:
Problems solved
I solved my problems. I installed the "custom" bootloader for each Rom and the "black screen" problem is now gone.
Thanx anyway.
drefcom said:
Thanks for the reply DefQon, I agree I think this is most annoying errors I have ever gotten.
I also searched high and low and could only find the fix for HC.
I have tried this method and works perfectly!
Thank you sooo much!!!
Click to expand...
Click to collapse
I have tested the fix for weeks now and it worked great.
Except, this afternoon my tablet randomly restarted and now won't go past CM 10 boot screen.
Any idea whether reflashing the ROM without wyping, purely just installing (as is) CM10 M2 from CWM? Or any other ideas?
I have tried clearing the cache and the dalvik cache. I then tried doing a factory reset but it doesn't seem to proress. I thought if I can do a factory reset then reinstall the ROM I might get it to work but I can't install the ROM as it says "Error (Status 7)?
I have tried formatting the /data in attempt to get the factory reset to work but this also freezes.
Currently, my tablet is in an infinite loop cycle and I cannot change the ROM or do a factory reset.
Thanks, you guys have really been helpful!
drefcom said:
I have tested the fix for weeks now and it worked great.
Except, this afternoon my tablet randomly restarted and now won't go past CM 10 boot screen.
Any idea whether reflashing the ROM without wyping, purely just installing (as is) CM10 M2 from CWM? Or any other ideas?
I have tried clearing the cache and the dalvik cache. I then tried doing a factory reset but it doesn't seem to proress. I thought if I can do a factory reset then reinstall the ROM I might get it to work but I can't install the ROM as it says "Error (Status 7)?
I have tried formatting the /data in attempt to get the factory reset to work but this also freezes.
Currently, my tablet is in an infinite loop cycle and I cannot change the ROM or do a factory reset.
Thanks, you guys have really been helpful!
Click to expand...
Click to collapse
After hours of trying I have found a solution.
I previously had done backups. I tried each one until one started restoring. It completed quite a lot till it froze and I restarted into recovery.
I did a cache wipe and dalvik cache wipe and could then complete a factory reset.
It has now booted completely into ICS where I can now flash CM10 again.
The tablet works normally as you would expect on ICS. I booted into recovery and tried to flash CM10 M2 for the GT-P7500 but I still get a error, status 7.
Anyone experienced this?
drefcom said:
After hours of trying I have found a solution.
I previously had done backups. I tried each one until one started restoring. It completed quite a lot till it froze and I restarted into recovery.
I did a cache wipe and dalvik cache wipe and could then complete a factory reset.
It has now booted completely into ICS where I can now flash CM10 again.
The tablet works normally as you would expect on ICS. I booted into recovery and tried to flash CM10 M2 for the GT-P7500 but I still get a error, status 7.
Anyone experienced this?
Click to expand...
Click to collapse
Status 7 usually indicates the wrong update file, are you sure you are flashing the right ROM for the 7500?
Perhaps try to flash the recovery and bootloader first and then the right ROM and see what happens?
DefQoN_BE said:
Status 7 usually indicates the wrong update file, are you sure you are flashing the right ROM for the 7500?
Perhaps try to flash the recovery and bootloader first and then the right ROM and see what happens?
Click to expand...
Click to collapse
The thing is it is the exact same file I used to flash the previous time.. I first updated my recovery and bootloader before flashing and still get the error. Thanx for the thought though.
I found the solution.
Really pisses me off that it was this simple.
Turn on your phone into bootloader
Leave it on bootloader until the battery drains 100%
You can tell it is drained when the phone looks like it is bricked and when you plug it in a red light shows on the notification light
Let it charge for ten minutes
Boot the phone
It should boot. Yeah. Seriously.
It looks like a battery fault of some sort. Welcome
YFBanana said:
So two days ago my Nexus 4 died, and i charged it back up. When I tried to turn it on, it would go to my boot screen, but it would bootloop for 5 minutes, and then restart. This never happened before even the other two times my phone died. I have tried doing a lot of things including switching PA for CM11, and getting stock everything from google. Everything goes succesfully, but again, for every different boot logo, it does the same thing. It really pisses me off beacuse i cant find anyone else with a similar problem, so i dont know what to do.. Also, since the thing cant boot, i cant even turn it back in to tmobile, because it is unlocked and they don't help with anything unlocked... any help would be appreciated Also, if i need to proivide more info on the software i can
Click to expand...
Click to collapse
Did you try to wipe Dalvik Cache & Cache in recovery after flashing back to stock?
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Click to expand...
Click to collapse
+1. And if that doesn't work and you have a hardware issue, boot into fastboot and use
fastboot oem lock
That'll lock the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google
It's the best way.
Click to expand...
Click to collapse
Well yeah, but flashing the stock rom just left me with a bootloop, just with those 4 rings..
boot into recovery, see if your computer detect your phone as android device, try use minimal adb and fastboot, it happen to me once, and success to fix it. if it cant fix it, try use nexus root toolkit, the tools here on xda nexus 4 forum. choose back to stock, and dont forget to choose current status as soft-bricked/bootloop. let me know how it goes.. we'll figure it out
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Update. I somehow managed to get it up and running on factory version 4.3 but I flashed/ used an older radio.img "cwm-radio-mako-m9615a-cefwmazm-2.0.1700.48.img" got it from here
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
and by using this method "[URL="http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312]http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312[/URL]
Many thanks to all the good ppl on here
Kdom81 said:
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Click to expand...
Click to collapse
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
YFBanana said:
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
Click to expand...
Click to collapse
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
I fixed it, and had it fixed for maybe 4 months, but now it is back in a bootloop. What i did to fix it the first time beats me, i just randomly flashed 4.4 roms, and it booted once. I used adb sideload for some stuff, but i am gonna keep trying.
Kdom81 said:
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
Click to expand...
Click to collapse
I cant even boot in 4.2.2...
I hate this so much.
Also, i just rebooted my phone and i got this loop again.
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
YFBanana said:
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
Click to expand...
Click to collapse
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
I am gonna try this now, i just hope it doesnt ruin my phone even more lol
22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
There is a problem, seems like the lg drivers are not compatible with windows 8.1...
Found a fix, check the forum page
First, some info about the phone. It's a SCH-I545, I rooted it the day I got it (I forget which method), still running stock, and it's been running great for months.
But a week or so ago, I grabbed my phone to use it, and noticed it was on the Android system recovery screen. So I pulled the battery a couple of times to restart, and every time it's same thing.
Does anyone have any idea how to fix this, or what I can do?
Thanks
drewsephvladmir said:
First, some info about the phone. It's a SCH-I545, I rooted it the day I got it (I forget which method), still running stock, and it's been running great for months.
But a week or so ago, I grabbed my phone to use it, and noticed it was on the Android system recovery screen. So I pulled the battery a couple of times to restart, and every time it's same thing.
Does anyone have any idea how to fix this, or what I can do?
Thanks
Click to expand...
Click to collapse
Mate ,
If every time reboot into recovery it may be soft bricked , did you try factory reset it? if that does not work you may have to reflash your rom again , if you are stock you have to use Odin
Can you enter download mode? If so flash custom recovery with odin (philz is best) download custom rom and put on external storage then Flash custom rom with new recovery
Sent from my GT-I9505 using Tapatalk
MAX 404 said:
Mate ,
If every time reboot into recovery it may be soft bricked , did you try factory reset it? if that does not work you may have to reflash your rom again , if you are stock you have to use Odin
Click to expand...
Click to collapse
Yep, every time. And I've cleared factory and cache, no dice
1eyedmonster said:
Can you enter download mode? If so flash custom recovery with odin (philz is best) download custom rom and put on external storage then Flash custom rom with new recovery
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice! Sadly, the usb port on my phone stopped working awhile back (I have to use an external battery charger), so I'm probably out of luck if flashing is the only way to go. I know there probably isn't one, but do you know of any way to flash something from sd?
drewsephvladmir said:
Yep, every time. And I've cleared factory and cache, no dice
Click to expand...
Click to collapse
does not look good , you may have to flash firmware again....
BTW all the push buttons on phone are ok? none of them is stuck? double check.....
drewsephvladmir said:
Thanks for the advice! Sadly, the usb port on my phone stopped working awhile back (I have to use an external battery charger), so I'm probably out of luck if flashing is the only way to go. I know there probably isn't one, but do you know of any way to flash something from sd?
Click to expand...
Click to collapse
You can flash a ROM from the SD card, but not recovery.
IF the USB port is fried and you can't get it to boot to the ROM, then I don't think you could get recovery on it.
MAX 404 said:
does not look good , you may have to flash firmware again....
BTW all the push buttons on phone are ok? none of them is stuck? double check.....
Click to expand...
Click to collapse
Holy...CRAP.
I dismissed your advice about buttons at first, but a few hours later when I was dismantling my phone for the hundredth time during the two weeks that it's been broken, I decided that it couldn't hurt to check. Sure enough, disassembled, all the internal buttons are fine.
The buttons on the phone's outter shell, however? Totally bent. I straighten them out, put it all back together, and power it on. And it WORKED.
Dear friend, and I do consider you a friend, you gave me back something I thought I had lost, something I couldn't afford to replace.
From the bottom my heart, thank you. Thank you so very much.
drewsephvladmir said:
Holy...CRAP.
I dismissed your advice about buttons at first, but a few hours later when I was dismantling my phone for the hundredth time during the two weeks that it's been broken, I decided that it couldn't hurt to check. Sure enough, disassembled, all the internal buttons are fine.
The buttons on the phone's outter shell, however? Totally bent. I straighten them out, put it all back together, and power it on. And it WORKED.
Dear friend, and I do consider you a friend, you gave me back something I thought I had lost, something I couldn't afford to replace.
From the bottom my heart, thank you. Thank you so very much.
Click to expand...
Click to collapse
Brother in Arms ......
Any time my friend , glad you fix it.