1.) When I rooted my phone, I originally flashed TWRP as my recovery. I then switched to CWR because I heard it was needed for CM10. Now when I open the ROM Manager app, it lists that I have both recoveries installed. Is this a problem? Can it cause any issues? Is there any way to remove TWRP so it;s not listed in ROM Manager?
2.) This may be normal, but I doubt it. When I power off my phone and plug it into a wall charger, it automatically boots to recovery for about 30 seconds and then automatically reboots my phone back to android (doesn't matter which ROM, stock or CM10 based. Although with CM ROMs it sometimes goes into a boot loop depending on the ROM). Even if I try and power off with the wall charger plugged in first, it goes to recovery and boots back up automatically., I have no way to charge the phone with the power off. Is this normal? Does it happen to anyone else? Does anyone know a way to stop it?
Thanks for any help on either question.....
flyinjoe13 said:
1.) When I rooted my phone, I originally flashed TWRP as my recovery. I then switched to CWR because I heard it was needed for CM10. Now when I open the ROM Manager app, it lists that I have both recoveries installed. Is this a problem? Can it cause any issues? Is there any way to remove TWRP so it;s not listed in ROM Manager?
2.) This may be normal, but I doubt it. When I power off my phone and plug it into a wall charger, it automatically boots to recovery for about 30 seconds and then automatically reboots my phone back to android (doesn't matter which ROM, stock or CM10 based. Although with CM ROMs it sometimes goes into a boot loop depending on the ROM). Even if I try and power off with the wall charger plugged in first, it goes to recovery and boots back up automatically., I have no way to charge the phone with the power off. Is this normal? Does it happen to anyone else? Does anyone know a way to stop it?
Thanks for any help on either question.....
Click to expand...
Click to collapse
1) TWRP and CWM both work fine. Try uninstalling, then re-installing ROM Manager... though I'm not sure I really understand what you mean by "it lists that I have both recoveries installed". Are you sture it's not just informing you of the latest CWM available through ROM Manager (which is not newer than posted in my CWM thread)?
2) This issue is already listed under "Known Issues" for both CWM and TWRP. If you let the phone do it's quirky boot into recovery, but then just leave it alone, it will shut down and charge while the phone is off.
1.) I'd have to grab a screenshot, but I am 99.999% sure it says something on the bottom about recoveries installed and it lists both CWR and TWRP. It hasn't seemed to cause any issues. I was just curious if it might and/or if anyone has ever seen this.
2.) Did not know this was a known problem. I thought maybe I did something wrong when I rooted the phone.
Thanks for the info....
Related
First off id like to say thanks in advance to any replies and also apologize if this has been posted previously (i searched and could not find anything that was helpful) I lurked around these forums when i had my x1 and im hoping you guys can be as helpful for me as you are for everyone else. anyway onto the issue
I used the superboot method to root my ATT US Streak. My intentions were to update to 2.1 following the steps in the "eclair working on my u.s. unlocked streak!" thread (wont let me put a link since its my first post)
after using fastboot to root the phone will boot up and function fine but recovery and fastboot no longer work. i tried flashing Koush's custom recovery and other things that require fastboot and the terminal just says "sending..." nothing happens no errors or anything, the cmd prompt just sits there and i need to remove the battery to reboot the device.
i then downloaded the Rom Manager apk from the market and flashed the clockwork recovery from there (it said i did anyway). when i load the recovery from boot (volume keys + power and its the stock recovery) and chose option 2 to flash modaco custom rom or even the stock dell rom it just goes to a black screen and i once again need to remove the battery to reboot.
the phone itself is still functioning fine when it boots up and everything works the way it should other than the home, menu, and back button lights flash in random orders, thats just annoying though. again any help is appreciated
so what should i try next?
EDIT: woke up this morning and now the device will not turn on. i tried starting to fastboot and recovery but still nothing. plug it into my pc and i get the "found new hardware wizard" for a Qualcomm CDMA Technologies MSM.
first real brick? ha that would be my luck
EDIT 2: a kid just ran through my work, grabbed my phone and threw it on the ground. it screwed up the 30 pin connector on the phone and the charger. im going to hurt somebody. phone is booting again though... put sd card back in and still boots fine
SOLVED: Dont know the technical reasons behind it but i had to reinstall the drivers and switch usb ports for every fastboot and recovery procedure
removed SD card and its booting up normally. any thoughts?
Hey folks,
I'm having some issues with my ATT Atrix. The phone keeps rebooting at the "Rethink Possible" screen. I bought this phone off of somebody on CL. I actually had the phone make it past the att screen a couple times. It made it to the setup up Motoblur screen but when I clicked start it just skipped it and takes me to the "Emergency Calls Only" screen. However the phone would just restart eventually at this screen as well. When the screen timed out I could not get the screen to turn back on at this point unless I unplugged the USB cord and plugged it back in. When the phone was on the Emergency Calls screen, my computer did recognize the phone and it did launch the motorola website. While I had the phone at this screen it did say that it had to force close android.process.com. I am coming from a captivate with rooting and flashing roms so I am familiar with Android. I am just trying to figure out where the problem could be with my Atrix. I am hoping somebody can point me in the right direction. Thanks for your time!
Your best bet will be to SBF that back to stock. Have you tried that yet? If not search for RSD Lite and SBF in the forums. There are several links and guides.
Is it unlocked?
I am not sure if it is unlocked as I cannot get past the emergency call screen. However, I will search SBF and research that option of setting it back to stock. I know when I flashed roms on the Captivate I would enter into recovery mode. I see in the Atrix that I would have to use Fastboot? The only reason I am worried about flashing a rom is that the phone reboots on its own so I would not want to hard brick it if it rebooted during a flash.
If it's unlocked you should see the word "unlocked" in the upper left corner of the boot logo screen, unless it was unlocked then flashed back or fruitcake in which case it will not say unlocked.
You should not have issues flashing from recovery if you have enough juice in your battery, which you maybe don't if you have been letting it sit rebooting. The rebooting is more than likely caused by an issue with a kernel, ROM, etc. Think of recovery as being similar to the BIOS on a PC. You enter into BIOS before the OS boots, etc., and this is before all the hardware has initialized and drivers have loaded, so the problem causing the reboots should not exist at that time. I would definitely try flashing a different ROM, and also a stock kernel.
It never said unlocked when I got the phone to turn on. I am having trouble getting the phone to turn on this time. I have downloaded RSD Lite and the 4.5.91 .sbf file to flash. I am just having trouble getting the phone started. Are there any ways to force the phone on. When I press the power button the green LED stays lit but nothing comes on the screen. When I plug into the charger it shows the moto symbol then goes to the Battery charging screen. Im not sure if the battery is correct because it says BHX5 1500mAh on the battery. Thanks for your help guys!
Update: I can get the phone into Fastboot and then Android Recovery Mode when the phone is plugged into the wall charger. However when I connect the phone to the computer via USB it just shows the green led when the phone is powered on. Anyway I can get the phone to boot into Fastboot while connected to the computer via USB?
Bump. Any way to get the phone to turn on when plugged into the computer or anyone know why there would be an issue of the phone turning on when plugged into the wall charger but only showing the green led when plugged into the computer? The battery shows 100% charged. Thanks
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
nishith611 said:
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
Click to expand...
Click to collapse
Did you fastboot -w before flashing the sbf? (Guess you don't really need to when flashing a sbf)
What may also help is flashing the boot.img file from whatever ROM you are using via fastboot.
Don't know if this will help, but it solves an issue when flashing to a different ROM from CM7, so maybe will help for you.
I know this might sound dumb, but do you have a sim card installed? Also, try to boot into recovery and just do a factory reset. @CaelanT already pointed out that this should be unnecessary since you flashed an sbf but it wouldn't hurt to try.
nishith611 said:
Update: I got the phone into RSD mode and flashed the 4.5.91 sbf but the phone only goes to the Emergency Call Screen. Is there anything else that can be done?
Click to expand...
Click to collapse
EDIT: I reread the OP and realized he had already tried to bypass the start screen.
That is not the correct battery. That is actually a battery used for the Droid X/X2. It seems they have pulled a switch-a-roo on you. (Probably because the Atrix battery could be used as an "Extended" battery in the DX/DX2) Anyways, it should still work but you can find the correct battery online, it should be a BH6X and should have a capacity of 1880/1930mAH.
nishith611 said:
...Im not sure if the battery is correct because it says BHX5 1500mAh on the battery. Thanks for your help guys!
Click to expand...
Click to collapse
Thanks for the reply. I tried to get the phone into recovery mode. I get to the Exclamation Point screen but it gives me no options for a factory reset. I saw that you have to touch the lower right hand side of the screen, but this doesn't do anything for me.
As far as flashing the boot.img file for the rom that I used. I flashed the stock 4.5.91 motorola rom. How can I find boot.img and would I flash it using RSD?
Also would it help if I flashed a custom rom instead of the stock Motorola 2.3.4 rom?
Could the battery not being the BH6X rom be the issue for it not getting enough power to stay on by itself?
Thanks for the help guys, I really appreciate it!
No, the sim card was not installed during the flash. However, I did install the sim card afterwards but the phone boots up and goes to the big green battery charging screen and does not go any further. However when the sim card is not plugged in I can get the phone to go to the Emergency Call screen.
nishith611 said:
As far as flashing the boot.img file for the rom that I used. I flashed the stock 4.5.91 motorola rom. How can I find boot.img and would I flash it using RSD?
Click to expand...
Click to collapse
The following are the instructions for flashing the boot.img. this was the solution to bootloops when trying to restore to a different ROM after CM7, but as I said previously, you never know if it will help or not:
1.Open up the Zip file of your current Blur ROM (Ninja, CherryBlur, Alien, etc.)
2.extract the boot.img file and copy to the directory where your fastboot is.
3.Pull phone battery & reinsert
4.Power on phone and go straight to Fastboot mode (Power + Vol Down)
5.Type "fastboot flash boot boot.img" (exclude quotation marks)
6.Once flashed, reboot phone using "fastboot reboot"
Sorry, don't know how to extract the boot.img from a sbf. Did a quick search and couldn't find instructions. Not something I have done before. Maybe someone else can help with this. I don't even know if this will work, but anything is worth a shot when you are stuck.
<edit> Which CWM are you using?
You can flash Romracers via fastboot if you are not using it. This may help you get into recovery.
Update: I got the phone to recognize the sim card and make phone calls and get wifi active. But the phone still reboots by itself. I can use all the functions of the phone except it just reboots by itself. I got into the About phone section and it says
Android: 2.3.4
Kernel: [email protected] # 2
I can get into the Android Market as well as everything else. Could this be a hardware issue that causes the phone to reboot by itself within a minute or so?
Edit: I can get the vol up and down buttons to work while the phone is working but the power button is not responsive to let me power the phone off. Could a hardware issue with the power button be causing the constant reboot loop?
Update: I got the phone to function with the OS working just fine (phone calls, texts, emails, etc..) but it keeps restarting on its own. The power button still does not work however, could this be a hardware issue? Thanks
EDIT: As I've now gotten Odin to flash again, and my device still won't boot, I'm really starting to think Andromeda's recovery has wiped something vital that isn't restored with a "regular" stock ROM image. PIT? EFS? Partitioning? Something like that? Odin successfully flashes the whole image tar (which I've previously used successfully), and the boot splash now correctly changes to the default Samsung one without triangle, but still the phone won't boot (as described in msg #3). So I'm now wondering if there's any way to a more aggressive restore (whence the topic title change)? Or am I barking up the wrong tree here?
----------
Hi
Okay, so I was testing out different kernels with Paranoid Android. I had the Dorimanx kernel installed at first, but had some volume issues, so I shifted to the Dream kernel, wouldn't boot. Then then the Andromeda kernel, and it still wouldn't boot, so I thought I might try doing a factory wipe in Andromeda's recovery. It then froze, and after about 20 minutes I gave up waiting for it and reset the device.
I then tried using the recovery to reinstall the Dorimanx kernel that worked, but it would fail, too. Just hang. After some attempts, also at just mounting the storage via USB, everything would fail, a couple of times with a message about emmc not mounting IIRC.
I then got a response on PA's forum about which kernel was suggested, and the answer was the stock kernel, so I thought I'd just use Odin to flash a CF kernel.
I think I had to do two attempts, or maybe just one, but it succeeded in installing the kernel, and the device rebooted. Except it didn't really. I can't get a "regular" boot screen (the one with the triangle), and so I can't get into recovery. Also, when the charger is plugged in, instead of showing first the grey battery icon with the spinner in it (which I seem to remember would spin before) and the going to the battery with green, it just show the grey icon with a spinner that doesn't spin. It never goes to the green battery screen.
I could (and can) still get to download mode, so I thought I'd do a back to stock routine. I downloaded a full stock ROM and tried to flash it with Odin. It would then freeze at the setup connection step. I tried a different image, same result. I tried reflashing the CF kernel (which worked just minutes before with Odin), again with the same result. I tried different USB ports and cables (even though I just used Odin successfully before), rebooting, unplugging at the frozen step and plugging back in, but to no avail. Odin won't flash any .tar.md5 anymore AFAICT. At least not with the regular no-frills one-click approach.
I'm fearing a hardbrick here. Except I still have access to download mode, and Odin sees the device. Could the recovery in Andromeda have destroyed the partition table perhaps? Or overwritten something it wasn't supposed to?
Is there a different approach to recovery that I could try out? Or does any one of you have any tips I might try out? Anything would be most welcome and appreciated
Thank you,
Daniel
PS: Oh, I just tried starting it up after it's been without battery and unplugged overnight and all day. I tried starting it into recovery mode, and now I have a different screen altogether: It says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Well, that sounds tempting! Except - I've never used Kies on this device in the first place, and Kies does not having any clue what I've been doing with this thing... Would it be safe to try out? I'm hesitant...
Daniel Smedegaard Buus said:
Hi
Okay, so I was testing out different kernels with Paranoid Android. I had the Dorimanx kernel installed at first, but had some volume issues, so I shifted to the Dream kernel, wouldn't boot. Then then the Andromeda kernel, and it still wouldn't boot, so I thought I might try doing a factory wipe in Andromeda's recovery. It then froze, and after about 20 minutes I gave up waiting for it and reset the device.
I then tried using the recovery to reinstall the Dorimanx kernel that worked, but it would fail, too. Just hang. After some attempts, also at just mounting the storage via USB, everything would fail, a couple of times with a message about emmc not mounting IIRC.
I then got a response on PA's forum about which kernel was suggested, and the answer was the stock kernel, so I thought I'd just use Odin to flash a CF kernel.
I think I had to do two attempts, or maybe just one, but it succeeded in installing the kernel, and the device rebooted. Except it didn't really. I can't get a "regular" boot screen (the one with the triangle), and so I can't get into recovery. Also, when the charger is plugged in, instead of showing first the grey battery icon with the spinner in it (which I seem to remember would spin before) and the going to the battery with green, it just show the grey icon with a spinner that doesn't spin. It never goes to the green battery screen.
I could (and can) still get to download mode, so I thought I'd do a back to stock routine. I downloaded a full stock ROM and tried to flash it with Odin. It would then freeze at the setup connection step. I tried a different image, same result. I tried reflashing the CF kernel (which worked just minutes before with Odin), again with the same result. I tried different USB ports and cables (even though I just used Odin successfully before), rebooting, unplugging at the frozen step and plugging back in, but to no avail. Odin won't flash any .tar.md5 anymore AFAICT. At least not with the regular no-frills one-click approach.
I'm fearing a hardbrick here. Except I still have access to download mode, and Odin sees the device. Could the recovery in Andromeda have destroyed the partition table perhaps? Or overwritten something it wasn't supposed to?
Is there a different approach to recovery that I could try out? Or does any one of you have any tips I might try out? Anything would be most welcome and appreciated
Thank you,
Daniel
PS: Oh, I just tried starting it up after it's been without battery and unplugged overnight and all day. I tried starting it into recovery mode, and now I have a different screen altogether: It says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Well, that sounds tempting! Except - I've never used Kies on this device in the first place, and Kies does not having any clue what I've been doing with this thing... Would it be safe to try out? I'm hesitant...
Click to expand...
Click to collapse
the reason for Dream and Andromeda not booting ur phone is that, if ur paranoid rom version was latest, then it comes with the new JB mali drivers for which only Dori v7.4 and siyah v5.0 are compatible
since u have already messed up too much with ur phone, u can try the 'KIES' option as the last resort to restore it back, since odin flash is not wrk'ng for u
Okay, so I tried installing Kies and connecting it. A variety of connection attempts, but it just won't connect to the device.
But, I'm making some progress! I've found that when I can get the phone to boot into the "Firmware upgrade encountered an issue." screen, I can get Odin to flash the stock Gingerbread image (still won't in download mode). And I then get a reboot with the regular Samsung boot splash (no yellow triangle) - except it never gets past it. After about a minute, it'll go black and then boot back up to the same splash screen and the same problem.
This is the exact same image I've used previously to revert the device to stock. So I was kinda hoping to see a normal clean. But unfortunately no donut. It reminds me of a computer I once bricked by screwing with its BIOS - it never got beyond POST and so I couldn't reflash it.
Is there something like a BIOS in this thing that could've gotten damaged in some way? And if so, is there any way to use Odin or another tool to fix that?
Cheers,
Daniel
Tried flashing a couple of matching CF kernels. I now get the green battery after the grey one, but still no boot.
All turned out the be the Shun Andromeda kernel re-introducing the hard brick bug. If you have the same issue, see my reply here for links to where you can get the custom PIT trick up and running.
I'm havin problems with offline charging after i installed cm11. I've tried change kernel and change rom (i'm using PA rom now) and i'm still with the same problem.
When i plug the charger on my phone while turned off, it shows a battery icon with a question mark on it and i think it's not charging. Is this a general problem or did i make something wrong?
Try keeping it plugged in. See if it charges or not.
Also,did you change your bootlogo?
I didn't change my bootlogo. it boots motorola bootloader and then shows the battery icon with the question mark. I left my phone charging this way for a couple of hours and tried to turn it on. my phone booted with 0% battery and then shutted down, so definitely it is not charging. other thing I notice is that when my phone enter this buggy offline charging mode, I have to press power button + volume down to reboot my phone, it kind of get stuck in this mode when my phone enter it
Try using a different charger.
It doesn't seem to be a common issue.
Can you power up the phone whilst charger connected.?
I've tried two different chargers, one of my Moto X and the original one. If I want to charge the phone I need to turn it on first and then plug the charger. I can't turn it on with the charger on cuz it is stuck on that screen with the battery icon
I'm starting to think I've done something wrong. I did the following to get where I am right now:
I was on stock firmware, so I rooted the phone and installed the newest version of SS. Then I downloaded cm11 and gapps and copied to the phone. I entered the SS and wiped everything. After that I installed cm11 and gapps.
When I discovered that issue I've tried install JBX kernel to fix it and nothing. then I wiped everything again and installed PA rom + gapps and still that issue. Did I do something wrong?
No, you didn't do anything wrong.
Since its persistent across both ROMS, its not a ROM issue either.
In my opinion, its most probably a problem with port or the board. The port doesn't deliver enough power.
You can try flashing the stock ROM back, it might repair in case something s/w related is corrupted. If it doesn't work after that, then its a h/w glitch for sure.
just in case, if I install stock rom and the problem goes away, what might be causing this problem?
I can't re-flash stock rom because I can't charge my phone and I can't boot into the rom or recovery. I don't think fastboot charges my phone. I just realized that bootloader is locked. Maybe this is the problem, isn't it?
it isn't a h/w glitch because before cm11 it was OK to charge offline
You'll need a factory cable to flash in case your phone has insufficient power.
Look for it, there's a guide about making one in the general section I suppose.
No need, I've managed to charge the phone through USB on my pc. When I plug the charger on my phone, that glitch happens, but when I plug the USB on my pc, the phone lights up a white led and apparently it charges the phone (slower, but charges). That's really weird. I really want to know what is happening to my phone
Hello,
My razr xt910 had stock rom and MIUI on 1st slot using safestrap and everything was going well then today the device shutdown as the battery was low, When I connect it to the wall charger it boots just to the MOTOROLA logo "the first one.. before the safestrap menu" I mean there is no sign that its charging or so and when I connect it to the PC only the led notification goes on.
I left it for while on the wall charger then the screen goes off just after I unplug it from the charger and I'm not able to boot it up again. so I back to plug it again. after many tries I managed to boot to safestrap recovery and changed the rom slot to the stock rom as I thought the problem with the MIUI rom restarted system and same problem happens.
and when I managed to pass the safestrap menu to the stock rom the device stuck at boot animation and either it keeps animating forever or it goes off after short time. tried to boot to fastboot menu (power+ vol down) it says battery low so...
- Is it really charging when it's connected to wall charger (showing moto logo) or when it's connected to the pc (led notification on) ? I tried to press vol down on both like some tutorial said but it didn't show the battery.
- After searching for solution, I didn't find the same problem happened to someone but similar ones that all were suggested to flash using rsdlite. can I flash different version of the stock one? I mean for my region there's 2 ics frimwares and I don't remember which one was the device on so it's ok to use any? Also if rsdlite is suggested in my case could you please provide detailed steps as I didn't use rsdlite or to flash frimwares before "was just flashing custom roms using SS". And how would I use while everytime I go to fastboot menu I see battery low msg .
- Could the problem be a battery's one? As the device sometimes goes off just after unplugging it and I can't power on it even I left it on wallcharger for like 30 mins.
Any help will be appreciated.
Thanks in advance.
I think RSDlite is the solution. So if your phone says low battery. There's a way to charge it with the normal charging cable. I bricked my phone about two months ago. I know that installing something wasn't the cause of this problem but i ALWAYS still any ROM or zip file with 80% charge, no less. Assuming that u still got the stock ROM and system folder. If not then it won't work.
1. Press power + vol down + vol up at the same time.
2. Go into AP fastboot
3. Press the power button. The screen should turn off at this point.
4. Plug in charging cable, after that the Motorola logo will show up. After that I don't remember if charging battery icon came up or screen goes black. I don't think it does. Sorry. But if does, then yay???
5. Let it charge for 1 hour or more. Just so that the charge is okay.
6.Check if its charging by going in AP fastboot and checking if battery is okay.
It worked for me on my spyder. Since I still had my stock ROM and my system folder wasn't deleted. If this doesn't charge then you have to buy one of those special charging cables.
If this works for you reply. IDK if installing firmware is different for xt910 but ik how to for xt912. It fairly easy.
---------- Post added at 05:16 AM ---------- Previous post was at 05:07 AM ----------
If I don't reply within 8 hours or more. It's because I'm still sleeping. Since it's 12am here in the US East.
GreatItami said:
I think RSDlite is the solution. So if your phone says low battery. There's a way to charge it with the normal charging cable. I bricked my phone about two months ago. I know that installing something wasn't the cause of this problem but i ALWAYS still any ROM or zip file with 80% charge, no less. Assuming that u still got the stock ROM and system folder. If not then it won't work.
1. Press power + vol down + vol up at the same time.
2. Go into AP fastboot
3. Press the power button. The screen should turn off at this point.
4. Plug in charging cable, after that the Motorola logo will show up. After that I don't remember if charging battery icon came up or screen goes black. I don't think it does. Sorry. But if does, then yay???
5. Let it charge for 1 hour or more. Just so that the charge is okay.
6.Check if its charging by going in AP fastboot and checking if battery is okay.
It worked for me on my spyder. Since I still had my stock ROM and my system folder wasn't deleted. If this doesn't charge then you have to buy one of those special charging cables.
If this works for you reply. IDK if installing firmware is different for xt910 but ik how to for xt912. It fairly easy.
---------- Post added at 05:16 AM ---------- Previous post was at 05:07 AM ----------
If I don't reply within 8 hours or more. It's because I'm still sleeping. Since it's 12am here in the US East.
Click to expand...
Click to collapse
Thanks for your reply,
now the problem is that I can't boot it when it's unplugged and when I try to do this while plugging, it still shows the same.. Moto logo without any sign to be charging.
Just saw some solutions that require me to open the back battery cover and connect the wires to the battery, but I'm really afraid to proceed with these steps to mess with the device :/
Also a solution said that the device doesn't charge like this, so I have to get a "factory cable" and do the rsllite thingy using this cable.
Is this method recommended? isn't there any easier way to try before proceeding with this ?
The easiest way to charge it is they way I said. But if you can't do that then factory cable is your other option.
GreatItami said:
The easiest way to charge it is they way I said. But if you can't do that then factory cable is your other option.
Click to expand...
Click to collapse
Thanks for your help :fingers-crossed:
Before taking the decision to make the factory cable I gave some tries because I'm not really experienced with this and wanted the easiest way to fix it. And I did managed to reach the safestrap menu and tried to charge it.
At first safetrap showed battery 99% after a while It changed to 5%+ I assumed it's charging that way and that actually was happening
I waited till it passed 60% and tried to reboot the system to stock slot but it I couldn't!! it stuck again at the stock rom's boot animation.
I forced to shutdown (power + vol down) then installed Liquid smooth rom that I had stored there and it was done successfully and I managed to boot into it. so now the problem is I can't boot to the stock rom but safetrap still works and I can boot to the any other slot. that means the problem I had before may occur again if the battery went low.
Now I will have to use rsdlite to flash the stock rom (unbrick it) right? If yes, Are there any steps that should be done first? I mean should I delete the other slots and keep only the stock one or it won't affect rsdlite?
Nex| said:
Thanks for your help :fingers-crossed:
Before taking the decision to make the factory cable I gave some tries because I'm not really experienced with this and wanted the easiest way to fix it. And I did managed to reach the safestrap menu and tried to charge it.
At first safetrap showed battery 99% after a while It changed to 5%+ I assumed it's charging that way and that actually was happening
I waited till it passed 60% and tried to reboot the system to stock slot but it I couldn't!! it stuck again at the stock rom's boot animation.
I forced to shutdown (power + vol down) then installed Liquid smooth rom that I had stored there and it was done successfully and I managed to boot into it. so now the problem is I can't boot to the stock rom but safetrap still works and I can boot to the any other slot. that means the problem I had before may occur again if the battery went low.
Now I will have to use rsdlite to flash the stock rom (unbrick it) right? If yes, Are there any steps that should be done first? I mean should I delete the other slots and keep only the stock one or it won't affect rsdlite?
Click to expand...
Click to collapse
If you want to get stock back then yes. Cuz I don't if installing a ROM on stock will fix it. But before you do anything,backup your files on internal storage to a computer.
GreatItami said:
If you want to get stock back then yes. Cuz I don't if installing a ROM on stock will fix it. But before you do anything,backup your files on internal storage to a computer.
Click to expand...
Click to collapse
Sorry for bothering you But I wanted to ask about something before starting the rsd to install the frimware.
Now as I told before I can boot to safestrap menu and can boot to other slots but not the stock one so...
- Can I install the frimware using safestrap?
- Should I try to boot the stock recovery and try a factory reset to the stock rom? if yes, will that affect safestrap? I mean if it didn't fix the stock rom will I still have access to safestrap? in other words Will safestrap will be still installed after doing a factory reset from the stock recovery?
Thanks alot for your help
Nex| said:
Wanted to ask about something before starting the rsd to install the frimware.
Now as I told before I can boot to safestrap menu and can boot to other slots but not the stock one so...
- Can I install the frimware using safestrap?
- Should I try to boot the stock recovery and try a factory reset to the stock rom? if yes, will that affect safestrap? I mean if it didn't fix the stock rom will I still have access to safestrap? in other words Will safestrap will be still installed after doing a factory reset from the stock recovery?
Thanks alot for your help
Click to expand...
Click to collapse
Anyone? :/
Nex| said:
Anyone? :/
Click to expand...
Click to collapse
Have you tried booting in to Safestrap, switching to the stock Rom and then wiping Cache and Dalvik? I would always try that before a factory reset. Also, if you are running the Xposed Framework in your stock slot the next step I would recommend is that you try flashing the xposed disabler. If you don't have the xposed disabler on your SD card you can download it from the thread that you originally downloaded xposed from.
swing4thefence said:
Have you tried booting in to Safestrap, switching to the stock Rom and then wiping Cache and Dalvik? I would always try that before a factory reset. Also, if you are running the Xposed Framework in your stock slot the next step I would recommend is that you try flashing the xposed disabler. If you don't have the xposed disabler on your SD card you can download it from the thread that you originally downloaded xposed from.
Click to expand...
Click to collapse
I've just switched to the stock and wiped Dlavik and cache (by safestrap) and still same problem... stuck at boot animation
I've never installed xposed before.
Shall I do a factory reset through the stock recovery or it will delete safestrap?
Thanks you for your help.
Nex| said:
I've just switched to the stock and wiped Dlavik and cache (by safestrap) and still same problem... stuck at boot animation
I've never installed xposed before.
Shall I do a factory reset through the stock recovery or it will delete safestrap?
Thanks you for your help.
Click to expand...
Click to collapse
I Deleted my stock slot and installed SlimKat over it and Safestrap still so I think Safestrap must insert code between the bootloader and the actual Rom. but I'm not 100% sure. Do a nandroid backup of your Miui slot and then try it. you can always reinstall Safestrap if you lose it.