Hello guys ,
Im having batterry drainage on my p7500 .. i tried all solutions including removing google+ , wipe cache and data , wipe battery stats !!!!
It seems like my tab cant go into deep sleep !
2% each hour when the tab is locked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I didnt have this issue before on HC 3.2 but now i can see a difference with battery
I also tried methods on the general forums on how to fix this but i still cant get it fixed ..
I see its a kernel problem , is installing a new kernel like pershoots kernel or a1 kernel would fix this ??? And wich one is better ??
Thanks
Sent from my GT-P7500
same thing
Same issues for me, 40% in just 16H
I try A1 kernal + set cpu to min but nothing change, the abttary still drops down over sleep mode,
Also:
I read all posts in this thread:
http://forum.xda-developers.com/showthread.php?t=1817562
still with out any new,,,,
---------- Post added at 06:41 PM ---------- Previous post was at 06:28 PM ----------
Same issues for me, 40% in just 16H
I try A1 kernel + set CPU to min but nothing change, the battery still drops down over sleep mode,
Also:
I read other posts about that...
still with out any new,,,,
I have P7510 with stock ICS rom ITA and for now no drain. In standby with all off for 13h, 0% of battery drain. Have you update from OTA or with Kies? Have you full charged the battery before update? Have you hard reset before update?
No i just flashed over my hc 3.2 stock
Sent from my GT-P7500
Now my tab clocks at 1Ghz !!!!!!!!
Im thinking of getting back to HC 3.2 :S
georgesadam said:
Now my tab clocks at 1Ghz !!!!!!!!
Im thinking of getting back to HC 3.2 :S
Click to expand...
Click to collapse
You should try to hard reset the device but be careful to emmc bug possibility.
I Fix it,,,,,,
1- Backup all your data....
2- Downlaod "JellyBeanRom ICS v6" from here: http://forum.xda-developers.com/showthread.php?t=1813651&highlight=battery
3- Make a full wipe.
4- Falsh the "JellyBeanRom ICS v6" as Thread steps.
5- After the tab restart and finshing falshng rom, go to bootloader and make "Wipe Battery State"
6- I hope everthing is fine now.
Note: Also if you just Make a full wipe & reinstall stock rom, it's will fix the Battery drain.
This is my personal experience with this issue, and this is the solution that saved me
You should try to hard reset the device but be careful to emmc bug possibility.
Click to expand...
Click to collapse
Yes i will try that , i have the emmc bug on my tab
So i should factory reset at all ?
is installing the CWM from droidbasement cm10 will bring to the safe side ?
I Fix it,,,,,,
1- Backup all your data....
2- Downlaod "JellyBeanRom ICS v6" from here: http://forum.xda-developers.com/show...hlight=battery
3- Make a full wipe.
4- Falsh the "JellyBeanRom ICS v6" as Thread steps.
5- After the tab restart and finshing falshng rom, go to bootloader and make "Wipe Battery State"
6- I hope everthing is fine now.
Note: Also if you just Make a full wipe & reinstall stock rom, it's will fix the Battery drain.
This is my personal experience with this issue, and this is the solution that saved me
Click to expand...
Click to collapse
Ok nice i will try that and i will report back but first let me check and read more about that emmc brick bug
georgesadam said:
Yes i will try that , i have the emmc bug on my tab
So i should factory reset at all ?
is installing the CWM from droidbasement cm10 will bring to the safe side ?
Ok nice i will try that and i will report back but first let me check and read more about that emmc brick bug
Click to expand...
Click to collapse
Before hard reset you have to flash a safe kernel. If I have understood fine pershoot has told that his kernel is safe.
In order:
- flash cwm from odin
- flash safe kernel from cwm
- wipe data and cache from cwm
ok i will try that and will report back
Something similar here
View attachment 1325541
View attachment 1325542
Up to Yesterday i had no deep sleep then i decided to full wipe my tab and to flash stock rooted ics. But battery drainage is still here... I don't know what are in better battery stats that two problem that drain my battery!!!
Who help me???
Sent from my GT-P7500 using xda app-developers app
@trunks986
I tried installing a1 kernel found in the development section and it seems that its now fixed and now i finally can get my tab into deep sleep
Give it a try
Ok.... I ll try!!!
Same here wit stock ICS from Tmobile.
This A1 Kernel can be flashed with CWM over my stock ICS or do i need any special rom?
Tab stay "awake" all the time:
Change your ROM
I try before flashing A1 Kernel, but it's not solve the battery drains,,
I think The main cause of the problem is the Rom ver "XXLQ8" - italian ics
Because when I wipe my tab & flash "JellyBeanRom ICS v6" rom, My problem is gone,,,
and really my tab have long life battery now and it's sleep "like a baby".
So I still recommended that me be you try to flash another Ics rom ver.
RushdB said:
Same here wit stock ICS from Tmobile.
This A1 Kernel can be flashed with CWM over my stock ICS or do i need any special rom?
Tab stay "awake" all the time:
Click to expand...
Click to collapse
Try installing A1 kernel over your ics stock and i think it should solve your problem ..
steps :
1-Download a1's kernel found here : http://forum.xda-developers.com/showthread.php?t=1833136
2-Copy it to your galaxy tab
3-flash it through CWM -> Instal zip from sd card and search for it then choose yes
4-reboot your tab
it should work but if you still have the problem install the newest cwm and make a full wipe then flash JellyBeanICS rom from the android development forum OR flash back to HC 3.2 if you were happy with it
The problem seems to be for me with the italian ics kernel that keeps searching for a sim card even on airplane mode
georgesadam said:
Try installing A1 kernel over your ics stock and i think it should solve your problem ..
steps :
1-Download a1's kernel found here : http://forum.xda-developers.com/showthread.php?t=1833136
2-Copy it to your galaxy tab
3-flash it through CWM -> Instal zip from sd card and search for it then choose yes
4-reboot your tab
it should work but if you still have the problem install the newest cwm and make a full wipe then flash JellyBeanICS rom from the android development forum OR flash back to HC 3.2 if you were happy with it
The problem seems to be for me with the italian ics kernel that keeps searching for a sim card even on airplane mode
Click to expand...
Click to collapse
George, its the first time in my life that i prefer the stock rom over a custom one... i used to have cm9, but it was too buggy for me (screen flickering, sod, etc)...
Ive read a little about the eMMC bricking problem, do i have to worry About it when flashing jellybeanICS? I mean, i would have to do a full wipe before flashing... A1 Kernel does not affect eMMC, since it does not execute the wipe command, am i correct?
RushdB said:
George, its the first time in my life that i prefer the stock rom over a custom one... i used to have cm9, but it was too buggy for me (screen flickering, sod, etc)...
Ive read a little about the eMMC bricking problem, do i have to worry About it when flashing jellybeanICS? I mean, i would have to do a full wipe before flashing... A1 Kernel does not affect eMMC, since it does not execute the wipe command, am i correct?
Click to expand...
Click to collapse
Yes your safe if you flashed A1 kernel over your stock ICS but that's not enough , you need to have a safe CWM . Try using the cwm from droidbasement flash it and you should safe now ..
i did install A1 kernel first before wiping and flashing toldos ROM just to be on the safe side ..
Another Tips for slove it
I found another solution for this issue in this post:
Finale Solution for Battery Drain issue
Related
Hey Guys. Im kind of confused about our phone. To what extent do we have this hacked? Is BravoX the only custom ROM we can use, or can we use others? Thanks
Currently that is the only rom out.
Sent from my MB520 using XDA Premium App
Yeah, it looks as if our lone developer, Bandroidx has essentially abandoned us since finishing BravoX.
I understand slowing down work on further ROMs, but there hasn't been any talk, or an update in a long time now.
Hmm. That really sucks. Well, if anyone else needs someone to be their testing dummy, let me know. Im trying all I can to get us 2.3, but im afraid im not going to be much help. But im here, willing to brick my phone if need be in the name of science .
Sent from my MB520 using XDA App
Don't give up, look what i posted!!!!!!
http://forum.xda-developers.com/showthread.php?p=15177546#post15177546
HOLY FREAKING CRAP DUDE, YOU ARE THE BEST! Oh my god, if I could give you 30000000000000000000000000000000000000000 thanks, I would!
edit: Woops, Bricked. Flashing SBF, hope I didnt break anything too badly.
edit 2: Did it again, same error. What am I doing wrong? Should I be installing MIUI in Bandroid's custom recovery or custom recovery that comes with 2ndInit?
ripin150 said:
HOLY FREAKING CRAP DUDE, YOU ARE THE BEST! Oh my god, if I could give you 30000000000000000000000000000000000000000 thanks, I would!
edit: Woops, Bricked. Flashing SBF, hope I didnt break anything too badly.
edit 2: Did it again, same error. What am I doing wrong? Should I be installing MIUI in Bandroid's custom recovery or custom recovery that comes with 2ndInit?
Click to expand...
Click to collapse
You should be installing it initially in bandroidx's. Did you wipe data and cache? How far does it boot up?
After you install MIUI you have to use the defy recovery (I use the latest, not the stable), though some things might be broken since was made for the defy. You can make backups and restores, but I wouldn't recommend restoring anything until I post something on it.
If you have anymore problems, go over the the thread so others can see. Thanks
Ohhhhh alright, let me try again. I blew out my sd, took my a while to find another but im now using my mom's from her flipout.
How do I get to bandroid's recovery now that 2ndinit is installed? it just boots to BootMenu
ripin150 said:
Ohhhhh alright, let me try again. I blew out my sd, took my a while to find another but im now using my mom's from her flipout.
How do I get to bandroid's recovery now that 2ndinit is installed? it just boots to BootMenu
Click to expand...
Click to collapse
In the bootmenu, select recovery. Then select custom recovery. It should boot into bandroidx's.
Note: after you flash the MIUI rom, you have to use the defy recovery.
Alright. This threads kind of off topic already, but I have one more question. When I go into Bootmenu (Installed with Latest 2ndinit)>>Recovery>>Custom Recovery it goes into some Defy Recovery. When I install 2ndinit cwm stable, it goes into some greenish version of custom recovery, but I cant get into bandroidxs. I cant figure out how to get back into Bravo Recovery!
ripin150 said:
Alright. This threads kind of off topic already, but I have one more question. When I go into Bootmenu (Installed with Latest 2ndinit)>>Recovery>>Custom Recovery it goes into some Defy Recovery. When I install 2ndinit cwm stable, it goes into some greenish version of custom recovery, but I cant get into bandroidxs. I cant figure out how to get back into Bravo Recovery!
Click to expand...
Click to collapse
Is this before or after you flashed miui? This is the order it should be:
Install bandroids recovery
Install 2ndinit
Boot into the boot menu
Select recovery> custom recovery. (it should boot into bandroids)
Wipe data/cache
Install miui + lang pack
boot into miui
Now, since you installed miui, when you select custom recovery>latest/stable in the boot menu, it should be the defy recovery. The defy recovery is supposed to come up, it works on the bravo, it is fully functional. Use the defy recovery to flash zips and make backups/restore.
This is all before MIUI. I follow those steps exactly, and I get taken to this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ripin150 said:
This is all before MIUI. I follow those steps exactly, and I get taken to this screen
Click to expand...
Click to collapse
what 2ndinit version do you have? Is it the one downloaded from my thread? Because I think I have an older version posted.
does that recovery work. Try backing up and installing miui on that because the defy recovery is working for me.
Gahh, Brick. I get taken to the bootloader screen, with a message that says Err:A5, 90, 35, 00, 3D. Ill flash the sbf and try again.
ripin150 said:
Gahh, Brick. I get taken to the bootloader screen, with a message that says Err:A5, 90, 35, 00, 3D. Ill flash the sbf and try again.
Click to expand...
Click to collapse
sorry to hear that. how'd you brick it?
Good luck!
Haha, tried to flash with the Defy recovery. Cant figure out how you got to Bravo recovery with 2ndinit! Will it work if I install 2ndinit, then bandroidxs, them rebooted directly into his?
edit 1:Here I go, trying it now. Going to go ahead and flash cm7 instead of miui.
edit 2: Nope, brick again.
ripin150 said:
Haha, tried to flash with the Defy recovery. Cant figure out how you got to Bravo recovery with 2ndinit! Will it work if I install 2ndinit, then bandroidxs, them rebooted directly into his?
edit 1:Here I go, trying it now. Going to go ahead and flash cm7 instead of miui.
edit 2: Nope, brick again.
Click to expand...
Click to collapse
I don't think the order of installation matters. Good thing you have an sbf handy because you've been using it all day
Did you install the 2ndInit correctly? Which 2ndInit did you install?
Try this one:
Alright, installed that version, now it takes me to this cwm recovery (doesnt have ADB so no screen shot, but its exactly like this one(minus the By Hiapk))
ripin150 said:
Alright, installed that version, now it takes me to this cwm recovery (doesnt have ADB so no screen shot, but its exactly like this one(minus the By Hiapk))
Click to expand...
Click to collapse
is it bandroid's recovery?
I dont think so. Its supposed to have orange text, and say Moto bravo at the top isnt it? Have you ever seen that screen?
edit 1: Flashing anyway, nothing to lose
edit 2: Didnt work. Ugghhhhhhh, what am I doing wrong???? Ahh whatever, thanks for all your help, ill get it eventually.
EDIT 2.5 JUST HAD AN IDEA.
Hi, i have a galaxy note GT-N7000 which was running the stock GB out of the box. After updating to ICS using Kies, i rooted the phone and installed SU and it worked fine. I then tried to flash Kingdroid ROM v3 onto my phone after which the phone got stuck on the "Samsung Galaxy Note GT-N7000" boot screen. It does not even go into the boot animation. I cannot access the recovery however the download mode is still accessible. I even tried flashing a stock ROM using ODIN (GB & ICS ROMS) but the setup keeps hanging at the image....
I believe that it is the eMMC bug which i did not know of before flashing. I need help because i have no clue how to fix it and it would really be a pity as i cannot afford a new phone already. Help would be appreciated. Thanks.
OK slow down ,when you flashed it ,did it complete flashing kingdroid from CWM then you manualy rebooted? only to be stuck on samsung logo
or did it hang during CWM flash and rebooted on it's own?
Flash a stock rom with bootloader.
How did you root and flash a custom rom and not stumble accross the hundreds of threads/warnings about the brick/bug?
endingcolt007 said:
Hi, i have a galaxy note GT-N7000 which was running the stock GB out of the box. After updating to ICS using Kies, i rooted the phone and installed SU and it worked fine. I then tried to flash Kingdroid ROM v3 onto my phone after which the phone got stuck on the "Samsung Galaxy Note GT-N7000" boot screen. It does not even go into the boot animation. I cannot access the recovery however the download mode is still accessible. I even tried flashing a stock ROM using ODIN (GB & ICS ROMS) but the setup keeps hanging at the image....
I believe that it is the eMMC bug which i did not know of before flashing. I need help because i have no clue how to fix it and it would really be a pity as i cannot afford a new phone already. Help would be appreciated. Thanks.
Click to expand...
Click to collapse
What 's this setup you talk about? Did you use Odin to flash?
Sent from my GT-N7000 using XDA
endingcolt007 said:
Hi, i have a galaxy note GT-N7000 which was running the stock GB out of the box. After updating to ICS using Kies, i rooted the phone and installed SU and it worked fine. I then tried to flash Kingdroid ROM v3 onto my phone after which the phone got stuck on the "Samsung Galaxy Note GT-N7000" boot screen. It does not even go into the boot animation. I cannot access the recovery however the download mode is still accessible. I even tried flashing a stock ROM using ODIN (GB & ICS ROMS) but the setup keeps hanging at the image....
I believe that it is the eMMC bug which i did not know of before flashing. I need help because i have no clue how to fix it and it would really be a pity as i cannot afford a new phone already. Help would be appreciated. Thanks.
Click to expand...
Click to collapse
You skipped the part about being on a safe kernel before flashing Kingdroid. Did you do that or did you use the stock ics kernel to flash kingdroid? You should always read!
tibosee said:
Flash a stock rom with bootloader.
Click to expand...
Click to collapse
MR.change said:
OK slow down ,when you flashed it ,did it complete flashing kingdroid from CWM then you manualy rebooted? only to be stuck on samsung logo
or did it hang during CWM flash and rebooted on it's own?
Click to expand...
Click to collapse
when i flashed the kingdroid ROM v3 using CWM touch, everything was fine. The installation completed and then i did a factory reset/wipe and cleared cashe & battery stats & dalvik cashe. After that i rebooted the phone and it never went past the "Galaxy Note GT-N7000" screen. I have tried flashing stock ICS & GB ROMs but they all keep hanging up at image.fs. So is my Note indeed hardbricked?
endingcolt007 said:
when i flashed the kingdroid ROM v3 using CWM touch, everything was fine. The installation completed and then i did a factory reset/wipe and cleared cashe & battery stats & dalvik cashe. After that i rebooted the phone and it never went past the "Galaxy Note GT-N7000" screen. I have tried flashing stock ICS & GB ROMs but they all keep hanging up at image.fs. So is my Note indeed hardbricked?
Click to expand...
Click to collapse
As a last resort try flashing stock gingerbread with bootloaders using ODIN. If that fails you can try partitioning method as suggested by hg42 or take your device to Samsung service center and tell them it bricked while doing factory reset from settings. Motherboard replacement time.
Sent from my GT-N7000 using Tapatalk 2
prasad.adam said:
As a last resort try flashing stock gingerbread with bootloaders using ODIN. If that fails you can try partitioning method as suggested by hg42 or take your device to Samsung service center and tell them it bricked while doing factory reset from settings. Motherboard replacement time.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Ive already tried flashing stock GB with bootloader but it hangs up at "factoryfs.img"! I guess i will have to take it back to Samsung Service Center. But will they charge me for it because the custom binary download shows "1 count"?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try this method but with GB files....
or try flashing a GB kernel then stock ROM with bootloader
good luck..
endingcolt007 said:
Ive already tried flashing stock GB with bootloader but it hangs up at "factoryfs.img"! I guess i will have to take it back to Samsung Service Center. But will they charge me for it because the custom binary download shows "1 count"?
Click to expand...
Click to collapse
No, they won't know binary count. So go ahead.
Sent from my GT-N7000 using Tapatalk 2
I would advice you to reset the counter.. try this...
http://forum.xda-developers.com/showthread.php?t=1354888&highlight=triangle+away
you may need to find/make a jig... and follow instruction to the letter..
OK ! If you are completely not successful with everything posted here ......
Try to goto Uggies thread for recovering from a EMMC brick
http://forum.xda-developers.com/showthread.php?t=1661590
Before that try reinstalling any GB Rom incase you are not emmc bricked.
Download AbyssKernel 3.9 and then do a cwm install of a GB kernel ....
Incase you got ur download mode ready, flash the Abyss kernel or let me know I will guide you thro ADB ..
i tried flashing stock GB ROM with bootloader but now my phone completely refuses to turn on. I think it is bricked for good! i have reported this problem to samsung without mentioning that i installed a custom rom. I told them that the error occurred when i upgraded from GB to ICS. However they are going to charge me a good $50-100 to get it fixed for software issue but even more if hardware problem! I really am in no position to pay so much as i purchased the Note only days back. Will this be covered under warranty and will they know tht i had flashed a custom rom?
why dont u try my thread on bricks ?
See my signature linked to bricks
This definitely works- i've used it and you simply use the patched pit file to flash your rom using pc odin. http://forum.xda-developers.com/showthread.php?t=1667886
youtube .com/watch?v=WH--qVK2h3g&feature=youtu.be
(there is a space between youtube and .com)
dave18 said:
This definitely works- i've used it and you simply use the patched pit file to flash your rom using pc odin. http://forum.xda-developers.com/showthread.php?t=1667886
Click to expand...
Click to collapse
No it doesn't - it works for a select few people. If your damage is in another area, it won't work. If the damage spreads (it has for some people), it won't work. Many people who did that found their device to be highly unstable afterwards.
Sent from my GT-P7510 using Tapatalk 2
and the thread title should be changed. he bricked his device while flashing from an unsafe stock kernel, not from kingdroid.
Hey i am having a problem with flashing this rom.
My current SGS specifications:
Android version: 2.3.7
Baseband Version I9000XXJVK
Kernel Version: 2.6.35.14-g7a2264a [email protected]#1
Mod Version: CyanogenMod-7-11162011-NIGHTLY-GalaxyS
The problem i am having is that when i got into CWM and i flash either cm9 or aokp or jellybean or whatever that is running 4.x.x i get several seconds loading something in CWM (flashing) and then it reboots , after that the boot animation twinks and it load several more seconds, and i goes into CWM again but really fast i was able to take a photo of it with my camera. ( at the end of the post )
So i tried flashing it from my external sd card, but with no luck again. Everything seems to go ok but after flashing it gets stuck in boot animation load screen. I tried flashing different versions of cm7 and everything goes ok. For example i did cm7.1 cm7.2 nightly builds everything flashes as it should but i have problems flashing to 4.x.x
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help me
"Can't open /sdcard/.."
"No such file or directory."
I think your file is corrupted, try re-downloading.
Maybe you should take your external sd card out and try to flash from internal sd card again.
Sent from my GT-I9000 using xda app-developers app
Methods that I know
The reason that I know are:
1. Some of the ROM required you after the Install it .. to re-install it again .. so do re-install.. but If you can't then..
2. It's mean CM7 is not compatible to move from ROM to ROM with different kernel.
My advice:
Flash it to Ginger bread using stable base band like XXJVU or so in Odin, then flash CMW with the same program, then you good to go to ICS ROM or Jelly Bean ROM.
Hope I helped
Aren't you just getting caught in a boot loop. Flash the new ROM again and then when it keeps re-boots and gets stuck just take the battery out and re-flash it. Will work
Sent from my GT-I9000 using xda premium
Yeah, its normal that cm9/10 flashes just for a second and then enters a bootloop for the first time. Just get out of the loop by removing your battery and flash the exact same file again.
The problem i am having is that when i got into CWM and i flash either cm9 or aokp or jellybean or whatever that is running 4.x.x i get several seconds loading something in CWM (flashing) and then it reboots , after that the boot animation twinks and it load several more seconds, and i goes into CWM again but really fast i was able to take a photo of it with my camera. ( at the end of the post )
So i tried flashing it from my external sd card, but with no luck again. Everything seems to go ok but after flashing it gets stuck in boot animation load screen. I tried flashing different versions of cm7 and everything goes ok. For example i did cm7.1 cm7.2 nightly builds everything flashes as it should but i have problems flashing to 4.x.x
Please help me
hi there
- Upgrading from CM7
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
this is the basic stuff when installing a rom above ok.
But ask yourself several questions before intsalling another rom ok ? does my rom work correctely, if not, you will insatlling a new rom on a not working one , do you get errors at all ? if so reinstall the stock and go straight to cm9 to have a clean base to continue with . this i had to learn the hard way , i went from cm7 with errors to trying to install cm9, and of course the errors will still be there in cm 9. so start clean ok .
But what you have to know is when coming from a rom like cm7 (did this my self like 30 times ) to another like cm9 or even cm 10 is that when you install first time , you install it in two stages ok .
first you try to install the rom cm9, which as you did went into a boot loop which is normal ok (its such a change form gingerbread to ics everything changes) ,
what you do then is go back into recovery ( using the 3 way combo ) and reinstall the same rom cm9 again , the second time its will install completely ok . easy and there you have it .
then install the google apps after that then reboot your phone , sometimes after rebooting your phone, it will again go into a loop and wont reboot correctely (often it will take a while before something happens not more than 5 minutes anyway ). If so, then take out your battery, wait for like ten seconds then replace battery again then boot your phone normally, then it should start normally with all the notiforcations like updating system ok. if it doesnt then take out battery again and retry ok .
then you have your brand new phone lol
p.s follow the steps and you cant go wong ok
see ya
if you need any help just pm me no problems,
Hi, i recently got myself an acer a500 16gb and decided to root it, i successfully rooted it using ics root 2, then i decided to try and install custom bootloader and rom onto it. to which i was successful, i tried a few roms, and after i had installed the 3rd rom, it started to stick on cyanogenmod loadscreen.
the bootloader i was using was skrilax's bootloader v8, and recover was TWRP.
it seemed that no matter what rom i used, it would install successfully, but always fail to get past loading image ( android / CM logo )
I then decided to reflash the bootloader to a different bootloader, this time, i used skrilax's bootloader v6 with CWM-based recovery v5.5.0.x (thor2002ro rev1.7) at this point i was successful, so i installed a JB rom with GAPPS, all worked well.
worked perfectly until about after an hour or so of use and a few restarts. the tab crashed, so i turned it off by holding power button, tried to turn back on and well, you guessed it, it wont boot...
i tried to reflash again, but every apx bundle i use it says " exact error "bootloader.bin" access denied.
im annoyed with my tab now, ive been searching through xda dev forums for about 3 weeks now and everything ive tried hasnt helped, and i cant find the answer to my problem, i hope theres someone out there who can help me through this lol.
thanks alot!
Did u do a full wipe of data between each new Rom u flashed?
If u still have the v6 or v8 on there, u could try connecting to yr pc and running fastboot to erase userdata, cache and system partitions. Once u erase system your tab will have no OS, so flash a new rom.
Otherwise, run the babsector file making sure u do the wipes between each .bat file and then flashing a new Rom.
It's good practice to fully wipe data and cache before a new Rom flash, and this should be stated in the Rom install instructions.
The babsector file and fast boot steps can be found in the root guide in my sig.
Sent from my HTC_PN071 using Tapatalk
dibb_nz said:
Did u do a full wipe of data between each new Rom u flashed?
If u still have the v6 or v8 on there, u could try connecting to yr pc and running fastboot to erase userdata, cache and system partitions. Once u erase system your tab will have no OS, so flash a new rom.
Otherwise, run the babsector file making sure u do the wipes between each .bat file and then flashing a new Rom.
It's good practice to fully wipe data and cache before a new Rom flash, and this should be stated in the Rom install instructions.
The babsector file and fast boot steps can be found in the root guide in my sig.
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
yeah, i did full data wipe as well as cache and dalvik cache.
at the moment, my tab seems to be stuck in APX mode as i turn it on, no vibrate, screen lights up but stays black and way to get into the bootloader (PWR + VOL - dont work either )
I will have a look now and try with babsector, I just hope i can get it back to a custom rom, if not, back to sock BL and ROM.
matty93 said:
yeah, i did full data wipe as well as cache and dalvik cache.
at the moment, my tab seems to be stuck in APX mode as i turn it on, no vibrate, screen lights up but stays black and way to get into the bootloader (PWR + VOL - dont work either )
I will have a look now and try with babsector, I just hope i can get it back to a custom rom, if not, back to sock BL and ROM.
Click to expand...
Click to collapse
I tried babsector and i get this?....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what do i do?
Put it in the oven....I joke u not!!! U have a faulty memory chip, which explains yr tab acting weird. The only apparent fix ?? is to reflow the solder around the chip, this seems to have helped a few folks who've tried it. There's a thread round here somewhere, I'll post it if I can find it
Sent from my HTC_PN071 using Tapatalk
---------- Post added at 09:29 AM ---------- Previous post was at 09:24 AM ----------
matty93 said:
I tried babsector and i get this?....View attachment 2769872 what do i do?
Click to expand...
Click to collapse
There's this thread http://forum.xda-developers.com/showthread.php?t=2617196 but I'm sure there's another one around here too....good luck !!!
Sent from my HTC_PN071 using Tapatalk
dibb_nz said:
Put it in the oven....I joke u not!!! U have a faulty memory chip, which explains yr tab acting weird. The only apparent fix ?? is to reflow the solder around the chip, this seems to have helped a few folks who've tried it. There's a thread round here somewhere, I'll post it if I can find it
Sent from my HTC_PN071 using Tapatalk
---------- Post added at 09:29 AM ---------- Previous post was at 09:24 AM ----------
There's this thread http://forum.xda-developers.com/showthread.php?t=2617196 but I'm sure there's another one around here too....good luck !!!
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
So, i have put it in the oven and followed the instructions to the T and it allowed me to flash with skrilax's bootloader v8, ive tried to install one ROM so far ( CM mod Acer A500 unofficial ) and that just gets to the cyanogenmod boot screen and hangs there, im gonna reflash with same bootloader, but a different rom. any suggestions?
Did u do a full wipe b4 flashing the Rom,?? I do know that the first boot does take a long time, did u try a reboot, sometimes that helps with th CM roms, other than that m8, maybe try a different one???
Sent from my HTC_PN071 using Tapatalk
dibb_nz said:
Did u do a full wipe b4 flashing the Rom,?? I do know that the first boot does take a long time, did u try a reboot, sometimes that helps with th CM roms, other than that m8, maybe try a different one???
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
yeah i did full wipes of everything, left it to try boot for 2 hours, nothing... tried different roms, now im back to "APX" mode... what do i do, i jus want it working again
M8 I think youve exhausted all possibilities...there's not a lot u can do with a faulty memory chip other than sourcing a new mother board. EBay is yr only hope...
Sent from my HTC_PN071 using Tapatalk
---------- Post added at 12:17 PM ---------- Previous post was at 12:13 PM ----------
If you're in 'proper' apx mode I.e. download mode showing on screen...could try running nvflash from there... If yr on black screen with led lite on power off - hold in pwr button for 5 secs till lite goes out. Should be able to pwr on normally now
Sent from my HTC_PN071 using Tapatalk
I wanted to get imperial kernel v3.3 since they added a google services battery fix
Ran script wiped etc... Phone just stays on model number inital boot screen. :0 This also happened on a stock root rom i tried.
Hybridmax works great but ive got passive battery drain and its a bit outdated. With hulk i cant get wifi working Maybe if tw v2 comes out itll work!? . Kushan seems unstable.
I was hoping imperial would patch the problem yet still no changes :/
any advice?
Try this.
*Update your recovery.
*download the zip again
*flash the file
*clear cache and dalvinks.
*remove the battery and keep it away for 1 min or so.
*place the battery again and turn the phone on
Revert.
DeepankarS said:
Try this.
*Update your recovery.
*download the zip again
*flash the file
*clear cache and dalvinks.
*remove the battery and keep it away for 1 min or so.
*place the battery again and turn the phone on
Revert.
Click to expand...
Click to collapse
I tried your advice before with no results.
Im guessing if trying on a clean install of a different rom had the same problem then the issue lies in a strange place
The other rom was a stock with root :0 so im guessing king of similar to what im running now. Maybe the stock roms have some problems ?
LyQi said:
I tried your advice before with no results.
Im guessing if trying on a clean install of a different rom had the same problem then the issue lies in a strange place
The other rom was a stock with root :0 so im guessing king of similar to what im running now. Maybe the stock roms have some problems ?
Click to expand...
Click to collapse
versions 3.4 resolved the issue i hope my battery life will be as good as everyone says