Database Users

The ROM Manager cost me a days frustration

Started with Unlocked, rooted AT&T used in Italy.
Been away from XDA for a while, but decided to update my Atrix which was modified to my liking when I got just after release day. The rebooting for no reason and the lack of VOIP support convinced me it was time to upgrade to 2.3.4
Anyway I installed The ROM Manager and tried to make a backup, it crashed.
Tried to "fix permissions" and the phone died... I mean really died... Soft brick :-(
Since I am a noob it took me all day to figure how to get it back to "normal" by flashing back to old OEM .SBF file and thereafter upgrading to ATT-2.3.4_Pudding_preroot.
I set it up did the tethering thing the Root thing in windows command Ect.
Now for the issue... Updated a lot of things and thought that THIS would be a nice time to back-up my rom and tried The ROM Manager again.
It will not boot up in recovery mode (wanted to do the WEBTOP hack) and when I tried to do a backup the bastard phone died AGAIN..... Boot Failure 2 and nothing you do can change it??? Press volume up / down both together with power or not.... NOTHING...
Resulted in another flash and then all all over again with Rooting Ect...
What is wrong with this bastard "The ROM Manager" program and am I the only one running in to this?????
I will now remove this program but it did really seem like such a handy one to have...??
Sorry if this post comes out a little negative but this thing just cost me a otherwise perfect Sunday :-(
Robert

Fastboot flash rom racer recovery. Your recovery is probably bad.
I voided my warranty and your mum.

When I first got my Atrix, I downloaded ROM manager and flashed CWM recovery from it, and Got the "Failed to boot 2" error as well. I had to pull the battery and it rebooted just fine. Not sure a full sbf flash was necessary.
But like Pukemon said.. flash rom racer's recovery..

Sorry to display myself as a real noob / newbie again, but I have searched "Fastboot flash rom racer recovery" in various formats and have not found the "golden solution" anybody who have a link or a "how-to-do" which will give me a SAFE way to do this??
If my recovery is bad does this repair it? do I flash another recovery? or how does this work.... and most of all will I be able to use and run The Rom Manager when done?
Thanks in advance
Robert

http://forum.xda-developers.com/showthread.php?t=1204500

You'll do fine Robert and if you need help I will do my best. Just pm me if you would like help.
Sent from my MB860 using xda premium

Razr M XT 907 - Multiple Problems after flashing with RSD Light

Hey guys so I am facing weird problems. I have searched through the forums either I cant find anything or I am too scared to do any more experiments I really dont want to loose my Razr M XT 907.
Problems
Laggy performance at times
Camera gets stuck when I take pictures at times then I have to restart.
when I reboot my phone it shows AP Fast boot screen, then I have to access boot menu and select the second last option (Console something). It always shows Null:Null and when I change it back the phone reboots normally
Phone hangs sometimes and then responds with everthing I have clicked all at once.
The screen on off button responds a second late
I think you guys can help me better if I tell you what I did to this phone exactly since I got this phone.
What I did
I initially bought this phone with defaul OS 4.0.1 in Pakistan.
I then installed a Verizon system update of 250 MB that got my phone stuck on a boot loop (and made me cry almost)
I restored my phone to the settings it came in using this procedure
http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
The phone worked fine for 2 days but then I got that update prompt again and it got annoying so I though maybe If i upgrade it to JB using the same RSD Lite method but a different ROM that may solve it.
So I applied the above Procedure using this ROM
http://forum.xda-developers.com/showthread.php?t=2250155
The method showed as Passed on RSD Lite but the phone got stuck on bootloop again so I paniced and tried restoring my phone abck to ICS using the method mention in the first link provided.
Then the phone got stuck on AP Boot Menu
Then I used DROID_RAZR_M_Utility_1.20 and used both methods 1 and two but it didnt work
Then out of the blue I went to the boot menu and I saw an option Switch Console (Null:null) I pressed up key on and null null changed to default:tty something it and the phone booted up just fine back to ICS
Now everytime I power off the phone it goes to AP Boot menu showing FASTBOOT REASON: Sticky bit factory_fastboot and I have to do the above to restart the phone.
What I need
Please help me restore my phone I dont want to brick it, I am a simple user I will need step by step guide
Anyone ?

Bump
Bump still looking for a solution

I have CM10 on mine and the camera is completely broken

Enter fastboot oem fb_mode_clear and problem gone.

v0ltage112 said:
Hey guys so I am facing weird problems. I have searched through the forums either I cant find anything or I am too scared to do any more experiments I really dont want to loose my Razr M XT 907.
Problems
Laggy performance at times
Camera gets stuck when I take pictures at times then I have to restart.
when I reboot my phone it shows AP Fast boot screen, then I have to access boot menu and select the second last option (Console something). It always shows Null:Null and when I change it back the phone reboots normally
Phone hangs sometimes and then responds with everthing I have clicked all at once.
The screen on off button responds a second late
I think you guys can help me better if I tell you what I did to this phone exactly since I got this phone.
What I did
I initially bought this phone with defaul OS 4.0.1 in Pakistan.
I then installed a Verizon system update of 250 MB that got my phone stuck on a boot loop (and made me cry almost)
I restored my phone to the settings it came in using this procedure
http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
The phone worked fine for 2 days but then I got that update prompt again and it got annoying so I though maybe If i upgrade it to JB using the same RSD Lite method but a different ROM that may solve it.
So I applied the above Procedure using this ROM
http://forum.xda-developers.com/showthread.php?t=2250155
The method showed as Passed on RSD Lite but the phone got stuck on bootloop again so I paniced and tried restoring my phone abck to ICS using the method mention in the first link provided.
Then the phone got stuck on AP Boot Menu
Then I used DROID_RAZR_M_Utility_1.20 and used both methods 1 and two but it didnt work
Then out of the blue I went to the boot menu and I saw an option Switch Console (Null:null) I pressed up key on and null null changed to default:tty something it and the phone booted up just fine back to ICS
Now everytime I power off the phone it goes to AP Boot menu showing FASTBOOT REASON: Sticky bit factory_fastboot and I have to do the above to restart the phone.
What I need
Please help me restore my phone I dont want to brick it, I am a simple user I will need step by step guide
Anyone ?
Click to expand...
Click to collapse
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root

lulz
Adriantech said:
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root
Click to expand...
Click to collapse
Dude.. you know that you're responding to a thread that is literally a year old right?

cliMAKtic said:
Dude.. you know that you're responding to a thread that is literally a year old right?
Click to expand...
Click to collapse
And wath is the problem i cant help?

Adriantech said:
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root
Click to expand...
Click to collapse
I also have a solution, but you would need another phone...
But as cliMAKtic said, it's most likely way too late now. Same goes for your replies in other threads.
Adriantech said:
And wath is the problem i cant help?
Click to expand...
Click to collapse
You can, but I'm afraid you won't. You'll rather achieve the opposite by bringing obsoleted threads back to the top.

lem22 said:
I also have a solution, but you would need another phone...
But as cliMAKtic said, it's most likely way too late now. Same goes for your replies in other threads.
You can, but I'm afraid you won't. You'll rather achieve the opposite by bringing obsoleted threads back to the top.
Click to expand...
Click to collapse
ok

[Q] Alcatel one touch pop c7 - bootloop - imei invalid

Hi there xda members! i recently bought this alcatel pop c7 (1gb ram version) and like many others i soft bricked it - boot loop - while trying to install a ported miui, that was not good for my phone. So for 8 almost full days, im trying to recover my phone. Tryed every solution that i found here on xda and also other forums. At some point my phone wasnt even charging itself.
I have to mention that my phone was rooted and i have CWM 5.5.0.4 on it ( thanks to you guyz) . But cwm was of no use, backup restoration was of no use.
Finally found out a solution that created a biger problem for me (maybe this will help other users that have the boot loop issue) From the root request thread alcatel pop c7, i found about Cherry Mobile Fuze custom roms, and genesis did work. My phone boots now, it works fine, connects tot the internet but i have no sim detected, no imei and even mtk droid tools and imei generator didnt help (i think its because of the rom that is dual sim, on a single sim phone).
But as the thread from root request alcatel pop c7 sayd ( page 7 post 52) i had to replace boot img from stock and build.prop. Boot img was easy to find, build.prop not. So i took boot img from stock rom (posted here on xda, but bad scatter files) and build.prop i took from the first ported miui rom that bricked my phne. It boots now but no imei. mtk droid tools and imei generator aren't working, but the tutorials with mobile uncle tools, entering engineer mode and writing some comands there, that i think it may solve my phone, but too bad , my new rom has no engineering mode apk.
So im asking the xda comunity, is my phone done? is it gone? can i do something about it ?
Can i get a stock build.prop (maybe that was the problem)?. In my opinion i have a few options but dont know how to proceed in these cases : flash the stock rom (no good stock rom backup untill now, i have downloaded tons of backups) flash engineer mode to change those imeis (didnt find how to do it) use one touch upgrade to force update my phone to stock (is there any way to fool OTU that my phone has an older version of android or no version at all? are there a thing in build.prop that modified can make my phone seem outdated) and lastly a good build.prop.
Sorry for the long post, i wouldnt ever have bothered xda if i was not desperate (usually i find answers to my questions, but now nothing worked)
and also thank you in advance for reading, posting a comment , anything that can help me in my problem. Maybe the trick with genesis rom can unbrick others people alcatel pop c7 phones, but beware, imei may be gone after that.

help !!!
Can anybody help me please???

Alcatel Pop C7 stock Rom.
DragonfO said:
Can anybody help me please???
Click to expand...
Click to collapse
If your interested in unbricking your phone msg me on Instagram @Shevii_1.

Help used device spoof now note 4 wont start and wont flash

No need to explain why i needed to spoof my device but i tried editing the biuld.prop to sm-n9005 ( note 3) it didnt work but didnt chage it back as it made no difference other than chnage in device settins. so i downloaded device spoof and change it to another brand cant remmeber all i needed was for it to not be abote 4 cause of screen resolution and certain apps arnt compatable. anyway i spoofed it downloaded the app and the ask device spoof to return to previous and when phoone rebooted it stuck on the first boot screen note 4 android , so i thought i would reflash with stock rom but now when i try to flash it says Unsupported dev type on the phone and fails to flash.
is there away to reflash boot loader kernel or anything i can do as i think it wont flash cause it now thinks the phone is something different .
please have mercy have done this sort of thing in past with no problems i am thinking cause i didnt change the build prop back to the note 4 from note 3 device spoof has reflashed it to a note 3
or is there away to get odin to force flash and get past the phone saying unsupported dev type
any help trying to solve this would be very greatfull
I can get into download mode and the stock recovery but it says install anything from sdcard is locked and adb is locked when i try to select them
thanks
steve
ps i think this is rught forum it did say for questions and help
update have installed a custom recovery but every time i try to install a custom rom it says the rom is for a trltexx and my devie is a trlte ? accoring to google search this is the same thing ??? whats gives lol
managed to install a custom rom it installed but when it booted it did the same just stayed on the first boot screen the samsung note 4 andthen vibrated and rebooted does not even get to the samsung logo, what gives why would it do this ? have cleared cash all sorts dont overlook me a u think i am a newbee please as i have flashed other phones never had a problem other than a boot loop that was sorted with wipein cash files. this has me stooped surely a dev can give some help please you would be top of my list for christmas cards lol

sorry everyone turns out the site that said the stock rom was for my phone was wrong managed to get the stock rom from better site and now phone currently been set up again as we speak on stock rom just need to root it then can install the app as i manage to download the app and will change the resolution using adb next time instead of trying to use a shrt cut by using an app that obviously is not suitable for all phones that it is used on as a number of people have reported the same thing.
thanks everyone and this is my lesson to be learned

OK, this is a loooong story. Can someone save my xperiac4?PLS...........

I have a xperia c4 e5303, is a awesome device and 5-6 days ago i wanted to use xposed firmware to enable a fake gyroscope.
AND THE HELL STARTED.
I had the device rooted with custom recovery twrp when i was in lollipop 5.1, i installed the firmware for xposed and the phone was stucked in "android optimization", for hours. I restarded it sometimes but nothing, so i formatted my device and when i rebooted it, i was stucked in "sony" logo screen, some minutes ago i founded that my phone was totally empty.
c: *internal screaming*
I waited the next day, i downloaded the ftf of original marshmallow 6.0 firmware for sony xperia c4 and i installed it on my device, then everything worked perfectly luckely.
Easy peasy lemon squeezy, or not?
Some hours after i founded that i couldn't use the recovery mode!
I searched and searched and i founded that the problem could be the bootloader,so i used a sony official guide to unlock that.
I couldn't finished that guide becouse with any connection, on any computer, android sdk can't install his components(such as google usb driver, that are required for that method), and the program just install everytime the same package in loop. I tried aaaallll the method in the universe for that, i tried also to install once per once the zip files of the downloaded package but it was totally useless.
So i founded another method after some days of searching (with flashtool) and now my bootloader is fully unlocked, if i use flashtool to unlock the bootloader, it says that is unlocked and ask me if i want to relock it so i think now the bootloader unlock is done. FINALLY.
Then, i turned off the phone and started it by pressing the volume down+power botton, and all the device did was reboot himself repitetly until i release hard keys and when i do it the phone start automatically.
I think my device now reboot himself instead of going in recovery mode.
What can i do i am totally frustrated about this and i really don't want to buy a new device becouse i don't have a gyroscope. I love my xperia c4, i just don't know why i can't get the recovery mode back to install twrp, for rooting the device, for retry to get xposed virtual sensor and then finally enjoy my vr experience...
In the end, i have a Xperia C4 5303 with original Marshmallow 6.0 firmware installed, that can't go in recovery mode in any ways.
Pls someone help me..

no one?..
No one here know hot to save my smartphone?

update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..

asnachan said:
update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..
Click to expand...
Click to collapse
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs

thx
Bludwurst said:
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs
Click to expand...
Click to collapse
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..

asnachan said:
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..
Click to expand...
Click to collapse
Ah. You should've mentioned it (i.e. linked to the guide). Sorry sorry!
Read further down. The "recovery.from.boot.p" is this thing that overwrites TWRP with the stock recovery. Following the «THIS IS IMPORTANT» indication are instructions to get rid of the thing, and so being able to keep TWRP permanently.
You need that last step to succeed.
Sent from my Motorola Moto G using XDA Labs

in the other thread they said to me to roll back to 5.1 i am doing it now

nvm i got hard brick, the phone is dead and i can't enter in download mode....

asnachan said:
nvm i got hard brick, the phone is dead and i can't enter in download mode....
Click to expand...
Click to collapse
I'm very sorry to hear that ?
Sent from my Motorola Moto G using XDA Labs

Is fine, i had to buy another phone that is why is tarted to root the xperia.
just..i'm out from the world of rooting i think. i broke 2 devices 1 by flashing a original rom with sony original flashtool and 1 by installing a root with kigroot, and now on that i can't read the sim.
i wait until the world of rooting will be more stable and with more official custom roms...

RIP