Related
Okay so, since I'm sort of new, I wanted to ask a few questions:
1. Is it possible to root xperia x8 with manufacturing date 11w48? At least at 95% chance. I'm a bit scared of the bricking part...
2. If it is possible, what kind of "ROM" (if I understood correctly) should I get?
3. If I get hard bricked/soft bricked what's the chance my phone will be still usable.
That's about it. Please don't rage at me for "OMG USE SEARCH BUTTON" type of thing.
I have tried doing it but no results found. Just threads and posts of people updating their.. ROMs I gues? Correct me if I typed anything wrong there.
But yeah, help would be appreciated. Thanks!
Jetboard said:
Okay so, since I'm sort of new, I wanted to ask a few questions:
1. Is it possible to root xperia x8 with manufacturing date 11w48? At least at 95% chance. I'm a bit scared of the bricking part...
2. If it is possible, what kind of "ROM" (if I understood correctly) should I get?
3. If I get hard bricked/soft bricked what's the chance my phone will be still usable.
That's about it. Please don't rage at me for "OMG USE SEARCH BUTTON" type of thing.
I have tried doing it but no results found. Just threads and posts of people updating their.. ROMs I gues? Correct me if I typed anything wrong there.
But yeah, help would be appreciated. Thanks!
Click to expand...
Click to collapse
1. You can safely root your x8 regardless of when it is manufactured, you will not brick it
2. You have 11w48 so it is very risky to unlock your bootloader, i suggest you flash ROMS that is for stock
3. If you get soft bricked you can flash the stock firmware back using flashtool or SEUS, if it is a hard brick, you need to go to the nearest Service center or use a JTAG
Swyped via Tapatalk 2
Thanks a whole bunch. I thought I cannot root because of my manufacturer date. But what is a flash ROM tho?
Jetboard said:
Thanks a whole bunch. I thought I cannot root because of my manufacturer date. But what is a flash ROM tho?
Click to expand...
Click to collapse
you can root your phone. but you can't unlock bl.
when you root your phone, you cam install cwm recovery. simply dl a rom for stock kernel and go to recovery and install(flash) the rom. remember to check the instructions first.
Just because i don't doesn't mean i can't.
All what I found until today was that if I cannot unlock BL I cannot install CWM recovery.
Maybe it is related to model - mine is Sony Xperia J. Y2012.
There is no fastboot available.
Am I wrong, can I have CWM, nandroid backup etc on stock ROM as only such one I may flash ?
F308 said:
All what I found until today was that if I cannot unlock BL I cannot install CWM recovery.
Maybe it is related to model - mine is Sony Xperia J. Y2012.
There is no fastboot available.
Am I wrong, can I have CWM, nandroid backup etc on stock ROM as only such one I may flash ?
Click to expand...
Click to collapse
this is for x8. not sure how it works on J. but yeah we don't havt fastboot either. but we can install cwm even with a locked bl. again that's for se x8.
edit: my advice is go to your phone's subforum. you'll get your answers there.
Just because i don't doesn't mean i can't.
Thank you. I understand that lot of things is device dependent but thought there are non-breakable rules, like gravity,
and what is possible to do under certain circumstances was one of them.
Need walk through XDA forum once more, maybe there is a hope.
F308 said:
Thank you. I understand that lot of things is device dependent but thought there are non-breakable rules, like gravity,
and what is possible to do under certain circumstances was one of them.
Need walk through XDA forum once more, maybe there is a hope.
Click to expand...
Click to collapse
there probably are a few unbreakable rules, but not being familiar with your device i can't guarantee that it's safe or it would work.
Just because i don't doesn't mean i can't.
Despite lot of reading I still am missing knowledge.
Question is:
What is fastboot ?
I found more than one definition of it and compiled into my own.
1.
Of course fastboot.exe is Windows binary (part of flashtool pack) which does certain type of work.
This is not what we are interested in.
2.
I concluded that:
- fastboot is one of modes into what android device can wake up. Just like linux can boot in different ways or Windows into single mode.
- this feature is encoded into boot.img, it is not separate android application.
- boot.img will work only with related kernel.img. They are like love and marriage (which is like horse and carriage - Bundy's).
- Sony sometimes disables stock boot.img to boot into this mode then without replacing boot .img it is impossible.
More comments ?
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Just because i don't doesn't mean i can't.
Okay, I got one more last question. Is this guide http://forum.xda-developers.com/showthread.php?t=906195&nocache=1 okay to use for rooting? I'm still trying to find the LATEST safe ones =/ I wonder if this one is okay.
Um, I tried that one it didn't work. It said some stuff are missing, then it exited randomly etc.. Can someone give me a link or a short/long guide which I can use that's latest? I do have some X8 drivers in a .zip file but no idea how to install them. Thanks in advance.
Jetboard said:
Okay, I got one more last question. Is this guide http://forum.xda-developers.com/showthread.php?t=906195&nocache=1 okay to use for rooting? I'm still trying to find the LATEST safe ones =/ I wonder if this one is good.
Click to expand...
Click to collapse
I rooted mine with this
Means its safe
Sent from my X8
Having few issues with the SuperOneClick thing... It sometimes randomly exits, tells me that some stuff are missing etc. Any help? =/
Ok so I recently rooted my HTC One and I think I might've bricked my phone. I tried out the Renovate ROM (I think it was the latest version) and it didn't work somehow, and my phone was stuck in boot, so I went into recovery, and factory reset but I accidently checked the button for system and then my OS was deleted. To fix that, I adb pushed Insert Coin ROM and flashed that, but when I booted my phone, it started up fine, but then after 10 seconds or so, the phone would just freeze and then reboot. I went back into recovery adb pushed the stock Sprint HTC One ROM and flashed that and the same thing is happening, but this time, when the phone turns on, it just shows a black screen with the notification bar at the top, and I can't use it in any way. It also freezes and reboots after like 10 second.
TL: DR
My Sprint HTC One keeps on freezing then rebooting after ten seconds, no matter what ROM I try.
Thanks in advance.
Yea....you understand you cant install gsm htc one roms. Thats what you did. Go download a ruu and run it while your in bootloader as i see adb is working for you
Sent from my HTCONE using xda premium
---------- Post added at 12:09 PM ---------- Previous post was at 11:57 AM ----------
Also no ur not bricked. A hard brick means the phone cant even power on. Its a brick. Unusable.
Sent from my HTCONE using xda premium
HTC_M7 said:
Yea....you understand you cant install gsm htc one roms. Thats what you did. Go download a ruu and run it while your in bootloader as i see adb is working for you
Sent from my HTCONE using xda premium
---------- Post added at 12:09 PM ---------- Previous post was at 11:57 AM ----------
Also no ur not bricked. A hard brick means the phone cant even power on. Its a brick. Unusable.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
I believe I have done the same thing as I am very new to this. Is there a link or something to find this ruu? and doesn't it need to be a certain one?
Like my phone is a Sprint HTC One. I am stuck in a boot loop and no matter what ROM I try it just keeps rebooting? Please any help would be greatly appreciated!
Check this thread for the RUU and instructions
http://forum.xda-developers.com/showthread.php?t=2250904
Khilbron said:
Check this thread for the RUU and instructions
http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!
Knixson said:
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin
GSM is the AT&T, T-mobile & international models....Sprint & Verizon are CDMA
O.M.J said:
fastboot flash unlocktoken Unlock_code.bin
GSM is the AT&T, T-mobile & international models....Sprint & Verizon are CDMA
Click to expand...
Click to collapse
Thank you! would I also need to install the open recovery twrp to gain root access as well?
Knixson said:
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!
Click to expand...
Click to collapse
You need to follow the dev instructions. If I were you though, I wouldn't do anything more until you understand some of the risks involved. A phone is a really, really inconvenient thing to have incapacitated when you're learning how to flash. For one, your device wasn't bricked (completely nonresponsive to input); for another, dev instructions are going to tell you to use fastboot (or a toolkit that runs fastboot for you).
Before you start again, you should learn how to use fastboot at the very least, and if you can, adb install/sideload (although it seems you tried that based on the OP). fastboot is often the only thing working if a flash goes awry.
A ROM is a ROM, no matter what device it's for. GSM/CDMA are separate network technologies that power your phone. In the U.S., Sprint and Verizon are the major CDMA carriers, while AT&T, T-Mobile, and essentially the rest of the world use GSM. The easiest way to tell the difference between the two is to remember if you needed a SIM card to activate the phone or not.
However, GSM and CDMA devices are set up differently on the software (and hardware, in terms of radios) side, and if you flash a ROM built for a GSM phone onto a CDMA equivalent, you'll probably break the device. For all intents and purposes, you should consider GSM phones to be wholly distinct devices. Also make sure you're only flashing ROMs built for Sprint, as there are often differences between Sprint and Verizon phones as well.
Knixson said:
Thank you! would I also need to install the open recovery twrp to gain root access as well?
Click to expand...
Click to collapse
yep...unlock, flash recovery, flash ROM
Rirere said:
You need to follow the dev instructions. If I were you though, I wouldn't do anything more until you understand some of the risks involved. A phone is a really, really inconvenient thing to have incapacitated when you're learning how to flash. For one, your device wasn't bricked (completely nonresponsive to input); for another, dev instructions are going to tell you to use fastboot (or a toolkit that runs fastboot for you).
Before you start again, you should learn how to use fastboot at the very least, and if you can, adb install/sideload (although it seems you tried that based on the OP). fastboot is often the only thing working if a flash goes awry.
A ROM is a ROM, no matter what device it's for. GSM/CDMA are separate network technologies that power your phone. In the U.S., Sprint and Verizon are the major CDMA carriers, while AT&T, T-Mobile, and essentially the rest of the world use GSM. The easiest way to tell the difference between the two is to remember if you needed a SIM card to activate the phone or not.
However, GSM and CDMA devices are set up differently on the software (and hardware, in terms of radios) side, and if you flash a ROM built for a GSM phone onto a CDMA equivalent, you'll probably break the device. For all intents and purposes, you should consider GSM phones to be wholly distinct devices. Also make sure you're only flashing ROMs built for Sprint, as there are often differences between Sprint and Verizon phones as well.
Click to expand...
Click to collapse
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS
Knixson said:
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS
Click to expand...
Click to collapse
1) If all you are doing is flashing Roms right now you don't need to s-off.
2) You flash the zip.
and I will second the notion that you should do a lot of reading before you do too much. This is an easy process to screw up if you don't know what you are doing and taking your phone out of commission can be a real pain in the ass.
Good Luck!
Knixson said:
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS
Click to expand...
Click to collapse
We all have to start somewhere. There are some good guides in the forums if you search though that will be a lot more comprehensive than the answers we can give in each individual thread.
1. S-OFF matters if you want to make changes to /system during runtime. For example, if you used a root tool like Titanium Backup to move an app into /system with S-ON, the phone would crash because it detected a security violation (improper programic access to a secured location). S-OFF disables that check. You can still flash ROMs with S-ON though since the protection isn't active to the same extent in recovery, although I think it will block writing to the radio. Don't monkey with it more than you have to though, because it's easy to really screw yourself over with the wrong combination of software (unsigned boot software and S-ON will really brick your phone).
2. Read the thread. Almost all ROMs though are distributed in a flashable .zip, meaning you copy it over to the phone's storage and install through recovery (or use sideload). You shouldn't have to use the .imgs ever, although it's a good trick to know (use fastboot flash <> <>.img) in case something goes wrong. I had to do this recently when my fubared my /system but didn't feel like reflashing the whole ROM, so I extracted system.img from the ROM I used and just pushed that to device.
Rirere said:
We all have to start somewhere. There are some good guides in the forums if you search though that will be a lot more comprehensive than the answers we can give in each individual thread.
1. S-OFF matters if you want to make changes to /system during runtime. For example, if you used a root tool like Titanium Backup to move an app into /system with S-ON, the phone would crash because it detected a security violation (improper programic access to a secured location). S-OFF disables that check. You can still flash ROMs with S-ON though since the protection isn't active to the same extent in recovery, although I think it will block writing to the radio. Don't monkey with it more than you have to though, because it's easy to really screw yourself over with the wrong combination of software (unsigned boot software and S-ON will really brick your phone).
2. Read the thread. Almost all ROMs though are distributed in a flashable .zip, meaning you copy it over to the phone's storage and install through recovery (or use sideload). You shouldn't have to use the .imgs ever, although it's a good trick to know (use fastboot flash <> <>.img) in case something goes wrong. I had to do this recently when my fubared my /system but didn't feel like reflashing the whole ROM, so I extracted system.img from the ROM I used and just pushed that to device.
Click to expand...
Click to collapse
Thank you everyone has been very helpful I am so glad I found this forum I really do appreciate all the info that has been shared with me!
So I will leave with one final question then back to studying, Do you know any really good beginner tutorials or anything to start at?
Thanks again people I have learned a lot just in this conversation
Knixson said:
Thank you everyone has been very helpful I am so glad I found this forum I really do appreciate all the info that has been shared with me!
So I will leave with one final question then back to studying, Do you know any really good beginner tutorials or anything to start at?
Thanks again people I have learned a lot just in this conversation
Click to expand...
Click to collapse
There was a really good one in one of the threads in the development section, but I can't for the life of me remember what ROM had it posted. I'll take another look for it later, but in the meantime I would try reading on XDA's wiki.
Oh I just remembered one more question. I have Viper ROM currently but if I wanted to ad a different one should I wipe the Viper first and install new one or would it install right over top of the Viper? Thanks any help is appreciated. You have been the best!!!
Knixson said:
Oh I just remembered one more question. I have Viper ROM currently but if I wanted to ad a different one should I wipe the Viper first and install new one or would it install right over top of the Viper? Thanks any help is appreciated. You have been the best!!!
Click to expand...
Click to collapse
You can flash over it (which is often called a dirty flash) but you are much better off wiping first. I usually use This tool. Just put it on your sd card and flash it before you flash your new ROM.
I believe this thread will help any and all Sprint HTC One owners if they are having bootloop problems and also answers to frequently asked questions lmao!! Thanks again everyone you ALL have been VERY HELPFUL!!!!
Knixson said:
I believe this thread will help any and all Sprint HTC One owners if they are having bootloop problems and also answers to frequently asked questions lmao!! Thanks again everyone you ALL have been VERY HELPFUL!!!!
Click to expand...
Click to collapse
also do a nandroid before flashing, so you have a fall back
Htc One Stuck In Cwm And Cant Flash A Rom
SO i Rooted my Htc one and now im stuck in Cwm and i cant flash a rom or anything i have tried to sideload a Ruu file onto my phone but that didnt work
SO i tried using the Rom Update Utility and that didnt work either
Im lost and stuck with a Htc One That doesnt work at all i have tried multiple methods but nothing seems to work please help me if you can im 100% new to this whole thing....
jake012 said:
SO i Rooted my Htc one and now im stuck in Cwm and i cant flash a rom or anything i have tried to sideload a Ruu file onto my phone but that didnt work
SO i tried using the Rom Update Utility and that didnt work either
Im lost and stuck with a Htc One That doesnt work at all i have tried multiple methods but nothing seems to work please help me if you can im 100% new to this whole thing....
Click to expand...
Click to collapse
Check PM
Hi guys,
sorry for bothering you guys, but at this point i'm pretty much desperate. I tried to root my Xperia Z since it brings oh so many wonderful possibilities with it and i was sick watching at all the bloatware floating around my screen. Anyway. Since i'm a total noob when it comes to phones i have been reading quite a lot of confusing stuff on the internet, especially here as this site was recommended to me by a friend.
Now i do have a bit of experience flashing PSPs and such, so i thought "you're not a total moron, how much more difficult could flashing your phone be ?". Guess i was wrong =)
I followed this instruction: http://www.youtube.com/watch?v=Vs2iPY0J4ZA
Yeah, i know, it's a video and all. But the thing is. I've by now read different guides all explaining the same thing. And every one of them put things differently, most of them claiming it was totally easy, but most missed a few steps. So i thought a step by step video tutorial would be quite easy to follow. And it kinda was, until ...
The unlocking failed. At the point where it was supposed to say "unlocked successfully", nothing happened. Just the cmd-line and then "---", which from my knowledge stands for "proceeding". To me it was stuck. And it kept standing there for about half an hour, when impatiance kicked in. Yeah, im dumb like that. So i close the cmd and tried to reboot my phone and got a bootloop just after the logo.
So i went into fastboot again and basically tried to unlock it again. This time successfully only after a few seconds (i guess this is how it's supposed to be, since that's what it was like in the video.) Still bootlooping though.
Now at this point i'm frantically troubleshooting and kinda feel like a monkey with a wrench. It should work, but maybe i'm just doing it totally wrong, since i don't know better.
So at this point, from reading even more stuff i'm trying to flash a stock firmware onto that thing by using flashtool (http://forum.xda-developers.com/showthread.php?t=2162907). This is the firmware i found from that thread: http://forum.xda-developers.com/showthread.php?t=2216743 .
Now before i make things even worse. Is there anything wrong with my approach, do i need to think about anything else ?
The idea in the first place was to install this: http://www.cyanfox-rom.com/2014/01/01/cyanfox-2-0-2/
In that regard, would that be the right thing to do now ?
If you've read this far, thank you for your time and dedication to help. I really appreciate it. If you need any more information as to what i've done, don't hesitate to ask. Chances are im lurking around desperately.
First, dont worry, your phone can be repaired with flashtool. You can download flashtool (find it on Xperia Z android development section) and download FTF firmware for your phone, 4.3 is newest. and just follow simple instructions how to flash (cant search now for the link)
If you want to use 4.3 and to be rooted you must first flash 4.2.2 10.3.1.A.2.67 firmware and then follow this tutorial http://forum.xda-developers.com/showthread.php?t=2458268
Thanks a lot. Flashing worked like a charm.
However the info still says: "Bootloader unlocking allowed=Yes". From my understanding that means it's still locked ? So it's back to square one ? Add frustration to depair now... seems like i don't understand the process or something...
longerdonger said:
Thanks a lot. Flashing worked like a charm.
However the info still says: "Bootloader unlocking allowed=Yes". From my understanding that means it's still locked ? So it's back to square one ? Add frustration to depair now... seems like i don't understand the process or something...
Click to expand...
Click to collapse
It's not working. Went into fastboot again, unlocked, this time successfully in 1.0s. And again bootlooping.
What am i doing wrong ? I just don't get it. From my understanding it should work normally and i should be able to proceed to root. And this would require me to start the device normally in the first place right ? Im on here right now: http://forum.xda-developers.com/showthread.php?t=2327472
But to be perfectly honest, at this point i'm guessing here. :crying:
Okay, next try, same experience. Do i need to do anything else after the unlocking ?
Do i have to reboot and just go into that root thingy and start the runme.bat ? Edit: Which isn't even possible since i can't boot.
OR do i need to flash kernel and stuff.
These are basically the 2 options that i found and i'm totally confused about which one i need to do as to me both are exclusive of the other ? I think i need to solve that bootloop issue in the first place, right ?
I think it's absolutely clear that i need help with this stuff
Hours later i'm still trying to get this working. However it just doesn't. Bootloop keeps happening.
Since i don't know if i made a mistake or not, i just chose to try to go on about the rooting. This doesn't work either. I tried to do it like in this thread: http://forum.xda-developers.com/showthread.php?t=2154310
From my understanding it's for the .350 fw,but also works for the one stock rom i downloaded earlier ? Can anyone confirm that ? I'm just guessing here, since there is no explicit information about that for noobs like me. At least i didn't find it.
Well anyway. I ran fastboot flash boot auto root blabla... and this is what it tells me:
sending boot... okay
writing boot... failed (command not allowed)
WHY ? Does this have anything to do with the unlocking process before ? Did it fail ? Am i just using the wrong fw ? Any pointers as to what i'm doing wrong here ?
I know i cannot demand any help, since you don't really get anything for it, but it really drives me crazy. So any help is highly appreciated. So please... pretty please ! Thanks in advance.
drunkennes veenser
bump - thanks for reading - let me know if you have any ideas.
If it's root you want, you do realise you don't have to unlock your bootloader?
Xperia Z
---------- Post added at 10:49 PM ---------- Previous post was at 10:47 PM ----------
Use this guide, easy to follow and 100% works...
Xperia Z
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
http://forum.xda-developers.com/showthread.php?t=2565850
Xperia Z
Thanks, might try that one if everything else fails. This is still a stock rom build with all the bloatware right ?
However i am trying to get to install Cyanfox (see a few posts ago). To my understanding an unlocked bootloader and root are both required.
Just to my understanding, does that mean, that my unlocking the bootloader failed ? Or why isn't it showing an unlocked bootloader in the Config ? Sorry if i am asking dumb questions, but i seem to be stuck and i'd really like to understand what i'm doing wrong.
Tomorrow a friend of mine will try to help me with all that, since he has some experience with customs on his phone (a S3 i believe). So he told me that he has no experience with the Xperia Z. I'll also would like to show him this thread for additional info. So if there's anything you can throw at us, that might help, please go ahead. Again, i appreciate your help.
Hi, I would try and get back to stock if possible..
You might want to download Sony Update Service and connect your phone up through that. If your bootloader is unlocked, then SUS wont let you go any further but if you are locked you will be able to repair firmware back to stock...
Please dont take this the wrong way but if you are new to flashing ROMs then it might be better for you to take things one step at a time.
What I mean is start off by just getting used to rooting stock ,, then try flashing custom roms when you feel more confident with the process and after you have tried flashing a few custom ROMs to see which one you like best (there are some great ROMs for locked bootloaders out there), If you really want to unlock bootloader then go ahead...
It just seems like trying to root, flash ROM and unlock bootloader all in one hit just multiplies the likelyhood of errors occuring and it can be difficult to pinpoint at what stage it went wrong..
Good luck ...
Onmehedson said:
Hi, I would try and get back to stock if possible..
You might want to download Sony Update Service and connect your phone up through that. If your bootloader is unlocked, then SUS wont let you go any further but if you are locked you will be able to repair firmware back to stock...
Please dont take this the wrong way but if you are new to flashing ROMs then it might be better for you to take things one step at a time.
What I mean is start off by just getting used to rooting stock ,, then try flashing custom roms when you feel more confident with the process and after you have tried flashing a few custom ROMs to see which one you like best (there are some great ROMs for locked bootloaders out there), If you really want to unlock bootloader then go ahead...
It just seems like trying to root, flash ROM and unlock bootloader all in one hit just multiplies the likelyhood of errors occuring and it can be difficult to pinpoint at what stage it went wrong..
Good luck ...
Click to expand...
Click to collapse
I think that hit the nail on the spot =)
Thing is, i am a really impatient guy, which isn't the best trait when "taking it slow". It's more like "i want the best, and i want it now"
Of course what's best can't be answered objectively and i can't pinpoint why i decided on that specific rom, but it looked awesome to me, so i just went for it and tried to read up everything i need to know to make it work I just didn't expect to fail at the very first step... that's kinda very very frustrating.
Anyway, i'll see what we can get done tomorrow and make sure to report back. Again, thanks a bunch !
Sooo, aparently i made a mistake in the cmd line. We don't really know what i did wrong, since the KEY was correct, although i wrote ".exe", my friend didn't, and instead of typing it letter by letter, he copied it (i didn't know how, lol). And it worked at first try, no idea what i did wrong. So that's done.
Rooting was also easy. Sadly we couldn't go on at this point, since i had to download a few more things first. So after that, i'm on my own again and, who would have thought, next problem's not far away.
Now i do have a problem flashing roms. Every rom i tried gave me a "status 7" error. Now i already searched up a solution that includes removing a few lines in the updater-script.dat. However that didn't work either. I'm pretty sure i followed the guides exactly. But at this point i kinda have to assume, that i'm even too dumb for that.
Any suggestions ?
Here's what the log says:
Mounting partitions...
Extract busybox...
Extracting firmware update image file...
Note: This may take a while (it stays here for some time, np though)
Formatting SYSTEM...
Extracting firmware update to SYSTEM...
Note: This may take a while (and again it does)
Performing finalizing tasks...
set_perm: some changes failed
Error in zip
(status 7)
Installation aborted
Maybe this might help, tell me if u need anything else
longerdonger said:
Here's what the log says:
Mounting partitions...
Extract busybox...
Extracting firmware update image file...
Note: This may take a while (it stays here for some time, np though)
Formatting SYSTEM...
Extracting firmware update to SYSTEM...
Note: This may take a while (and again it does)
Performing finalizing tasks...
set_perm: some changes failed
Error in zip
(status 7)
Installation aborted
Maybe this might help, tell me if u need anything else
Click to expand...
Click to collapse
what recovery are u using and which rom u wanna flash?
Gesendet von meinem Nexus 5 mit Tapatalk
Tommy-Geenexus said:
what recovery are u using and which rom u wanna flash?
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
downloaded latest cwm via rommanager, it says v6.0.3.0
To make things simple i tried flashing the suggested stockbased rom (http://forum.xda-developers.com/showthread.php?t=2565850)
But since i keep getting the same error with any rom i tried, i assume i'm generally doing something wrong.
longerdonger said:
downloaded latest cwm via rommanager, it says v6.0.3.0
To make things simple i tried flashing the suggested stockbased rom (http://forum.xda-developers.com/showthread.php?t=2565850)
But since i keep getting the same error with any rom i tried, i assume i'm generally doing something wrong.
Click to expand...
Click to collapse
The recovery is probably your problem.
Try using atleast twrp 2.6.3.0 or philz touch cwm or the latest cwm
you can use the dual recovery as well
Gesendet von meinem Nexus 5 mit Tapatalk
Tommy-Geenexus said:
The recovery is probably your problem.
Try using atleast twrp 2.6.3.0 or philz touch cwm or the latest cwm
you can use the dual recovery as well
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
Got cwm 6.0.4.5, worked great ! THANK YOU A LOT !!! :good::good: OH YEAH, double thumbs up ! And there's me thinking, the guide said get rom manager, the program knows where to find the latest version. Whatever, great forum, seems like i finally might have figured out what i'm doing, at least kind of
Now to exploring all the funny roms and apps. I'm so excited
PS: Since this solved, do i need to do anything else ? I've seen "Solved" being in the title. Can i do that or do i have to ask a mod ?
i saw you solved your problem but still have a look over THIS
Hey guys, I am having some problems going from JDX down to a 5.1 ROM. I cannot get data on any of the ROMS I am trying.
I have tried to download a few radios seperate and flash them at the start, or after the fact and still nothing. I also manually went to the apn to set it up but the correct one is already there and that didn't work.
Is there something I need to flash to make it work correctly? I'm stumped!
thanks!
none
Did you check and make sure the bootloader was configured correctly? I don't know if it even changes it, I will see what mine says. If you have to downdrage it, you will have to search further, I don't know how to do that on this particular phone
Read this http://www.gottabemobile.com/2015/06/15/5-reasons-to-skip-android-m-beta-preview/
Downgrading is a Hassle
If you do decide to try the Android M beta release, you’ll have to completely erase your entire device and start over from a fresh install of Android. Users will need to backup apps and pictures, transfer all their data, re-download everything and set of the device the way they’d like. Then, if you decide you want to go back to Android 5 Lollipop, users will need to erase the device and do this all over again. It can be quite the hassle, time consuming, and frustrating for those new to Android, or aren’t used to doing this often.
Here is a youtube vid on how to downgrahttps://www.youtube.com/watch?v=TazsmCuA5Cwde
BL moto-apg8084-71.08 (sha-32b8854, then the date it was made
baseband d4.0-9625-02.95
product variant shamu xt1103 32gb p3a0
cpu apq8084 esi.1
That's what mine says, and your issue does sound like the BL got changed
Sorry I'm not more help, but that's what comes to mind rightaway
wow thank you do much for replying. That is what I thought too. I had 0 problems before with any ROM then I decided to try the JDX M preview ROM and since then going back hasn't worked.
I tried to download several bootloaders and radios and flashing them and using the toolkit to flash them. No luck I will watch that video and read that post and see if it helps me any.
Again, thank you!
so I downloaded it his way and flashed it his way and I still get no data.
gah!
none
You flashed the stock RUU? right? you should have gone to a google page that had the stock roms in them, it had links as well on the YT link I gave you, try again, I watched the vid and the maker was talking pretty fast, if you still have issues DL teamviewer to your computer and I will get on your puter and help ya out
lol, downgrading the bootloader will do nothing. im on m, with the m bootloader, and have hone to 5.1.1 a few times. always keeping my m bootliader.
if your apn is 100% correct, id just boot up, and eventually youll catch the signal, as long as its not disabled, or data isnt disabled.
of course, your sim card cohld have gone bad. they do die every now and then.
musicman625 said:
You flashed the stock RUU? right? you should have gone to a google page that had the stock roms in them, it had links as well on the YT link I gave you, try again, I watched the vid and the maker was talking pretty fast, if you still have issues DL teamviewer to your computer and I will get on your puter and help ya out
Click to expand...
Click to collapse
Hi Hi sorry for the delayted response.
Basically for whatever reason no CM ROMS would work at all. I tried some AOSP ones and they are completely fine and have no problems with them.
I Downloaded ROM Manager and will give a look into other CM ROMs in a little while to see if it works.
Thanks so much for all the help!
Mackie011 said:
Hi Hi sorry for the delayted response.
Basically for whatever reason no CM ROMS would work at all. I tried some AOSP ones and they are completely fine and have no problems with them.
I Downloaded ROM Manager and will give a look into other CM ROMs in a little while to see if it works.
Thanks so much for all the help!
Click to expand...
Click to collapse
Glad you got it back
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
simms22 said:
lol, downgrading the bootloader will do nothing. im on m, with the m bootloader, and have hone to 5.1.1 a few times. always keeping my m bootliader.
if your apn is 100% correct, id just boot up, and eventually youll catch the signal, as long as its not disabled, or data isnt disabled.
of course, your sim card cohld have gone bad. they do die every now and then.
Click to expand...
Click to collapse
How do you like M? I was thinking about giving it a twirl, decided to wait until the bugs were gone, and it's more refined
Hello! I have a moto x4 bought on CLARO (brazilian) carrier that comes with their official ROM (with non uninstallable apps, etc). It's the XT1900-6 model, with Android 8.0 Oreo installed. Thing is, the moto x4 was updated to Android 9 Pie, the retail devices have started receiving through OTA over a year ago. But as mine is carrier branded, it depends on them to release the updates (motorola gives to them and they do whatever they want, modify and release or do nothing) and they haven't lanuched the update. So I am tired of waiting and want to know if I can just "unbrand" my phone by installing an official retail firmware to receive the update (or just install the Android 9 firmware directly). Can I just get the retail firmware from lolinet and flash it following a guide? Or this is not possible at all?
I think the problem would be in getting the non-Brazilian ROM to access Claro, or whatever carrier you are using down there. But I don't know.
KrisM22 said:
I think the problem would be in getting the non-Brazilian ROM to access Claro, or whatever carrier you are using down there. But I don't know.
Click to expand...
Click to collapse
But the ROM would still be brazilian. Check out this firmware on lolinet.com on /firmware/moto/payton/official/RETBR/XT1900-6_PAYTON_RETBR_9.0_PPWS29.69-26-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (As a new user, I cannot post links yet)
Ah, okay, I understand your question. But of course not having tried it I don't know the answer. Have you tried lmsa (see my sig) to see what if anything it offers you?
KrisM22 said:
Ah, okay, I understand your question. But of course not having tried it I don't know the answer. Have you tried lmsa (see my sig) to see what if anything it offers you?
Click to expand...
Click to collapse
I have not, but I tried to check it out right now, your link is giving 404 not found error.
LOL yes, I screwed up. Thanks. Try it now.
---------- Post added at 10:22 PM ---------- Previous post was at 09:51 PM ----------
I realized another possible prob - the ROM you have on there now is a (maybe) custom ROM made by Claro. Therefore some other ROM like the one you suggested, might not connect to Claro. Dunno...
KrisM22 said:
LOL yes, I screwed up. Thanks. Try it now.
---------- Post added at 10:22 PM ---------- Previous post was at 09:51 PM ----------
I realized another possible prob - the ROM you have on there now is a (maybe) custom ROM made by Claro. Therefore some other ROM like the one you suggested, might not connect to Claro. Dunno...
Click to expand...
Click to collapse
Yes, I think that is the case. But the model is exactly the same as retail, I can't think of why a retail ROM wouldn't work. I think it would be like I had bought the phone in some random store and put a Claro sim card on it, it would work.
Okay, I tried LMSA, it says my ROM version is up to date. But this is expected, as it would check for updates in the Claro channel, which has none. I want to change to retail ROM so it would check for updates in retail channel.
Back in the day, even before Android, I did something like this with an old Nokia phone. Phones used to differ the model number not only by region, but also by carrier. I don't remember the procedure exactly, but I flashed a retail number over the carrier number and used a Nokia support software like the LMSA and it recognised the phone as retail. It had an update to be installed, so I did and the phone "turned" into retail version. Of course none of this applies for modern smartphones, but I think it may be possible to do something similar.
I hear you. Not having the Claro ROM to flash back if it doesn't work, you would be simply taking a chance. And if the new ROM won't connect to Claro, you're stuck. I realize the big reason I am being so cautious here is that in my reading I had recently encountered a Claro phone that now wouldn't work, but of course I forget where I read that and what was done to the phone - maybe a custom ROM? I'll do a search and see if I find it again. Nope, nothing in X4, so I don't know where I saw it.
EDIT: no, I find nothing. it was something about (I think) they were on a custom ROM and it would connect to Claro only and very slowly, or something like that.
EDIT2: I'm advising you not to flash unless you have a clear way back.
You're right, you're being cautious. This is exactly why I registered in the forum in the first place, so I could discuss the matter with people more experienced before I do anything stupid, maybe even found someone who had already done what I'm trying to do. I appreciate your help.
ivooc28 said:
You're right, you're being cautious. This is exactly why I registered in the forum in the first place, so I could discuss the matter with people more experienced before I do anything stupid, maybe even found someone who had already done what I'm trying to do. I appreciate your help.
Click to expand...
Click to collapse
You're welcome! Yeah, caution is something too many folks don't have enough of and wind up with bricked phones. And even used, they're not cheap. Keep searching!!!
I will keep searching! Isn't there a way to just extract the current firmware I'm running to use as a backup?
Theoretically, maybe, but I wouldn't want to trust it(see modems comment below). You could
fastboot boot twrp.img
to temporarily get twrp and then boot to it, and then use it to do a backup, but you must make sure that you back it up to your SDcard since internal storage is often wiped during a flash. Then, theoretically if your new ROM doesn't work you could
fastboot boot twrp.img
back into twrp and restore that backup, but, again, I wouldn't want to trust it. I have used that to back up stock when flashing custom ROMs in the past, but I always had, and often used, RSDlite to flash a stock ROM to get me out of trouble. I believe RSDlite will work on an 8.x ROM on the X4 (I haven't tried it) but I know it will not recognize my phone at all now that it is at 9.0 RSDlite needs to be updated and I have no idea who is running that these days. One question I would have over the above is the particular modems being flashed - are they different in your Claro ROM, and if so, i do not believe they are backed up/replaced if you do a TWRP backup or restore.
"Okay, I tried LMSA, it says my ROM version is up to date."
Does it offer to download that ROM? If so, click the little down arrow and download it and see if you can access that and see if it looks like something that could be saved and flashed later. When I tried it a few days ago it looked like it was offering to download the same thing I had on. If so, that might give you a copy of the ROM you're on that you could flash to get back if need be - IF YOU CAN TRUST IT.
Nite. I'll check in tomorrow PM.
EDIT: of course I don't know if you can go from a partial Treble 9.0 back to a regular 8.x ... even if you have the stock ROM.
KrisM22 said:
Theoretically, maybe, but I wouldn't want to trust it(see modems comment below). You could
fastboot boot twrp.img
to temporarily get twrp and then boot to it, and then use it to do a backup, but you must make sure that you back it up to your SDcard since internal storage is often wiped during a flash. Then, theoretically if your new ROM doesn't work you could
fastboot boot twrp.img
back into twrp and restore that backup, but, again, I wouldn't want to trust it. I have used that to back up stock when flashing custom ROMs in the past, but I always had, and often used, RSDlite to flash a stock ROM to get me out of trouble. I believe RSDlite will work on an 8.x ROM on the X4 (I haven't tried it) but I know it will not recognize my phone at all now that it is at 9.0 RSDlite needs to be updated and I have no idea who is running that these days. One question I would have over the above is the particular modems being flashed - are they different in your Claro ROM, and if so, i do not believe they are backed up/replaced if you do a TWRP backup or restore.
Click to expand...
Click to collapse
You're saying that if the upgrade fails, then I would need to downgrade back to 8.x and that could be a problem, I see.
About the modems being flashed, I don't know if I understand it right. I believe the modems are the same here, regardless if I bought in Claro or retail. What I'm saying is, usually here in Brazil, if you buy a retail or carrier phone, either way you can put any (Brazil) sim card and the carrier would work. Of course that if a phone doesn't support specific LTE frequency bands by hardware, then it wouldn't work, but then it wouldn't matter if it is retail or carrier.
lmsa apparently doesn't give me option to download firmware, or maybe I didn't check it out properly.
ivooc28 said:
You're saying that if the upgrade fails, then I would need to downgrade back to 8.x and that could be a problem, I see.
About the modems being flashed, I don't know if I understand it right. I believe the modems are the same here, regardless if I bought in Claro or retail. What I'm saying is, usually here in Brazil, if you buy a retail or carrier phone, either way you can put any (Brazil) sim card and the carrier would work. Of course that if a phone doesn't support specific LTE frequency bands by hardware, then it wouldn't work, but then it wouldn't matter if it is retail or carrier.
lmsa apparently doesn't give me option to download firmware, or maybe I didn't check it out properly.
Click to expand...
Click to collapse
a) yes, might be a prob. Don't know.
b) if you know that then you can flash any Br ROM you want and connect to any carrier with it.
c) in lmsa, click flash (top tabs), then "go rescue". A box with fill-in-the-blanks pops up: fill in:
moto phone, moto X 4th gen, XT1900-6 (I believe it was in your case)
Hopefully some lines will appear and there will be a little down arrow thing on the right side saying download.
Click that and download the ROM. Once it is downloaded (DO NOT click rescue as that will wipe your phone), but go looking on your PC and see if you can find where it stored that download and grab/save it for yourself for possible future . I suspect it will be in c/users/<name>/local/motorola/"rom name" or something like that, not necessarily in local. It gives you part of the name so you could search your c:/ for some of that name to try to find it.
I wish I could be more specific as to its location but when I tried it with my phone this morning it said "This device is not supported" - I suspect that is because I just took the Nov 1 sec patch and there is no ROM out yet for it (lolinet doesn't have it yet - probably take another 2 or 3 weeks)(pretty lame imho, but it is what it is.
As to b) above if there are really that many folks using different carriers down there it seems that someone should know the answer to your question. Different website maybe, or post blatant "any one from Brazil here?" subject line in x4 , or search xda for Brazil. someone's gotta know! I don't believe LenAsh will swat you for a post like that if you link to this post and make clear your problem. A piece of the problem may be that the xda x4 forum seems very quiet . There may be 80 folks looking in but few are talking. Or, simply no experience in the matter and not wanting to encourage you to do something that will render your phone useless...