Develop Bugs

Just unlocked bootloader (S-ON) Some help please

I would apreciate some help here as i got really confused.
I just unlocked my bootloader from HTCDev just to discover that I cannot install custom recovery, I cannot have root access and there are no recent custom ROMs to install (I need a stable one but recent, not older than mine - 2.3.5)
Could you help me by answering, what's the point of unlocking bootloader if I can't have the above?
I need to use sdcard for apps but for this, Root is required which is not able.
I need custom ROM (if there is one which is fine tuned with better performance, battery, and lighter)
I need to use apps that need root access, i.e titanium backup, etc. how can I use them without root?

So is this forum really dead? I remember it was more alive a few months ago.
I'm abandoning my efforts since I have to recover the phone back to normal use but it's a pitty that things are like that here.

First things first........as a senior member you should know well to post questions in the General section ONLY
Second..... if you have unlocked the bootloader correctly(i know you might have done that), root via Doomlord's easy root kit....
As far as the recovery is concerned...use Rom manager..... it's the easiest way
And the "aliveness" of the forum is quite well as compared to other fora...... the other mid-range phones may have more roms but a majority of them are PURE KITCHEN WORK while others have a little framework changes in CM7..... so there's no extra choice as compared to our phones.....
If you want good roms, mindhaxer/einstein.frat's(they both are the same) roms are good sense ones
Or you can try CM7 or CM9 if you are an AOSP fan
I hope this long post is the answer to all your points in your 2 posts

First of all, thanks for answering.
Second, even if I posted in Q&A, I don't believe I would get any different answers and,
third and most important, I have done my reasearch thoroughly but couldn't find this part you mentioned anywhere so I was trying to gain root with many other methods like super tool, etc. Now, if those guides are not stickies how could I possibly know where to find those steps? they were not even in the first 4-5 pages of the WFS forum.
Yes as a senior member I decided it would be wiser to post here in order to have better chances but maybe I'm wrong.
Anyway, I have to thank you again because you guided me to find the DooMLoRD package which wasn't mentioned anywhere else and now in a few minutes I managed to root the phone which I abandoned a few hours ago.
I still insist though that this info must be gathered here as sticky otherwise new comers will always be confused and need years to manage something which in other forums is managed in minutes.

andreasy said:
First of all, thanks for answering.
Second, even if I posted in Q&A, I don't believe I would get any different answers and,
third and most important, I have done my reasearch thoroughly but couldn't find this part you mentioned anywhere so I was trying to gain root with many other methods like super tool, etc. Now, if those guides are not stickies how could I possibly know where to find those steps? they were not even in the first 4-5 pages of the WFS forum.
Yes as a senior member I decided it would be wiser to post here in order to have better chances but maybe I'm wrong.
Anyway, I have to thank you again because you guided me to find the DooMLoRD package which wasn't mentioned anywhere else and now in a few minutes I managed to root the phone which I abandoned a few hours ago.
I still insist though that this info must be gathered here as sticky otherwise new comers will always be confused and need years to manage something which in other forums is managed in minutes.
Click to expand...
Click to collapse
I agree with you I've been trying to figure out the rooting of this phone for the past two hours, I never bother posting for help as you always get scolded and people say duh use search which is really helpful.
I did I didn't find the answers. this forum is a bit of a mess tbh compared to the onex forum..

Cynabal said:
I agree with you I've been trying to figure out the rooting of this phone for the past two hours, I never bother posting for help as you always get scolded and people say duh use search which is really helpful.
I did I didn't find the answers. this forum is a bit of a mess tbh compared to the onex forum..
Click to expand...
Click to collapse
If you need any help from here just let me know. I have already root on my phone and it's quite easy once you have all the steps in hand.

Cynabal said:
I agree with you I've been trying to figure out the rooting of this phone for the past two hours, I never bother posting for help as you always get scolded and people say duh use search which is really helpful.
I did I didn't find the answers. this forum is a bit of a mess tbh compared to the onex forum..
Click to expand...
Click to collapse
I went from complete noob to unlocking, installing cwm and then a custom rom by doing a lot of reading in xda and other forums. The info is all there!
You expect to spend 2hrs reading and know how to root, you need to spend more time learning, and the more time time you spend the less chance of messing it up.
I spent a lot more than 2hrs and all went fine and I've never had a problem.
Sent from my Wildfire S using xda premium

andreasy said:
First of all, thanks for answering.
Second, even if I posted in Q&A, I don't believe I would get any different answers and,
third and most important, I have done my reasearch thoroughly but couldn't find this part you mentioned anywhere so I was trying to gain root with many other methods like super tool, etc. Now, if those guides are not stickies how could I possibly know where to find those steps? they were not even in the first 4-5 pages of the WFS forum.
Yes as a senior member I decided it would be wiser to post here in order to have better chances but maybe I'm wrong.
Anyway, I have to thank you again because you guided me to find the DooMLoRD package which wasn't mentioned anywhere else and now in a few minutes I managed to root the phone which I abandoned a few hours ago.
I still insist though that this info must be gathered here as sticky otherwise new comers will always be confused and need years to manage something which in other forums is managed in minutes.
Click to expand...
Click to collapse
Its not about getting an answer to your question. Its about keeping this section clutter free. Its the development section for a reason, and I'm mighty sure I'm not seeing a custom ROM in this thread.
So follow the rules and post in General or Q&A next time.
Sent from my E10i using XDA

Ok I see. Now I have 2 options: reply or shut up and leave. I'll do both.
Firstly I apologise for intentionally posting in the wrong thread (I had my reasons). I won't do it again, actually I won't post anything here again as that was a one time task for me.
Second, I see that you are ready and willing to give me lessons and increase your thanks meter between each other but before teaching me how much time of reading is necessary before you root, let me tell you that I was in xda long before you and I know very well both how much reading is necessary but I also know what the spirit of a community is. There are mods here who didn't get irritated as fast as you. From the speed of your answers I recognise that you must not be older than 25 which doesn't make you mature so @scott_doyland, your opinion is accepted but I was a noob on 2005 and I have performed the root procedure on more than 6-7 phones just by reading so I've done my homework plenty of times and you know what? You don't need 2 hours to root a phone. Actually I need about 30 minutes max including the reading I do on the instructions of each phone. Only on this forum I didn't find all the info gathered and before you jump answering on that, I'm not complaining about this but that's the reason I posted in order to get an answer and avoid the research of 200 pages. It's you guys that got inflamed about that. So take a lesson from a veteran who broke the rules. The idea of the community is to help each other even if the answer was given several times. Some people may not have the time to read or maybe they have read tons of info on other forums and they are visitors like me and can't spent the same amount of time in all forums for each phone they have to root. I'm adraid that if you can't accept this, you are also breaking the rules. Do you see my thanks meter? well, not even one of those thanks was taken from posts like yours. Every single thanks I got was from help providing to noobs and to people who didn't do their homework. Maybe you should visit some forums in the DHD section and see what the spirit of community is all about.
I'm sorry for disturbing the calm waters of your forum but you won't see me again anyway. As I said, I spent many hours on other forums of xda, that was a one time stop for me because I had to root this phone and leave and since this forum doesn't have the most friendly structure in regards to info availability (stickies, etc.) I had to ask. I apologised for posting in wrong thread but I also had to pass the message that people willing to become teachers will have to become students, that's why I answered
Now, go ahead, feel free to start attacking and exchanging thanks between each other. You see, I contributed to your community in my own way. Many of you will double their thanks meters by tomorrow. I don't have the time to continue discussion, I have other things to do so, mods, please feel free and delete this post at some point since it doesn't lead anywhere but just take my feedback if you want and organise better the structure of your forum (if you want).

Ok bro. I have a S-ON, Unlocked Bootloader just like you. There are no way to root after u unlocked bootloader (because u need to update to lastest Hboot in order to UBL). I'd tried all tools i can find on xda and NONE of them can be use to root. There also don't have any clear guide for S-ON with UBL show how to install custom rom and get root.
But after few days digging up the forum, i'd managed to install custom rom + root. I share with you:
After your phone bootloader unlocked via HTCdev, your phone sure will have either HBOOT-1.08.0099 or HBOOT-1.09.0099. You'll need a ClockworkMod recovery image on your computer to install rom + root. And you'll need a working Android SDK with Fastboot to do get ClockworkMod working on ur S-ON phone.
OK let's say now you have fastboot folder alr, and know how to use it.
1. Download lastest clockwork mod .img here: http://www.clockworkmod.com/rommanager
2. put the file .img just downloaded to the fastboot folder.
3. Turn off phone, then hold volume down + power ---> wait the menu searching for the zip file (of course we ignore this) then press Power again to go to fastboot menu.
4. connect phone to laptop via usb cable.
5. Open fastboot folder, right click choose open command windows here.
5a. If you are on HBOOT-1.08.0099:
Copy this and right click to the command windows, paste then enter, ur phone will automatic restart to CWM menu:
Code:
fastboot -c "mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata),[email protected](devlog),[email protected](hboot)" boot recovery-clockwork-5.0.2.8-marvel.img
5b. If you are on HBOOT-1.09.0099:
Copy this and right click to the command windows, paste then enter, ur phone will automatic restart to CWM menu:
Code:
fastboot -c "mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata),[email protected](devlog),[email protected](hboot)" boot recovery-clockwork-5.0.2.8-marvel.img
Ok men, now u just download any rom u like, put it to ur memory card and flash rom like normal.
Remember that, everytime u flash new rom, u need to repeat the whole process from step 3 to step 5.
Hope this can help you bro. Cheers for our S-ON
BIG THANKS to this topic http://forum.xda-developers.com/showthread.php?t=1374926
Dear guy, your topic not yet help me to S-OFF my phone, but it gave me the temporary solution to install custom rom. Cheers to ur good work!!!
P/S: to the thread creator: Why u gave up so early bro...Xda-developers is great forum.

Ok, because many people are confused and PM me about what's next after unlock, here's the answer. Don't try the Super Tool, it doesn't work. At least for some people.
Go here: http://forum.xda-developers.com/showthread.php?t=1321582
and use that script instead. It will flash Busybox and su to your phone. That's it. You have root acces then.
@Ghekua: If you have unlocked your bootloader then you have already installed the apropriate HBOOT. Just run that script from the post I attached above and you will have root access.
Edit: Oh, sorry, I read your post before edit and got different meaning. Anyway, thanks, I used the post above which is much faster and easier and I'm done.

Ghekua, if you install a custom rom it will already have root access, no need to root a custom rom.
I rooted my stock rom just by flashing cwm and then via cwm flashed a root.zip file from xda.
Sent from my Wildfire S using xda premium

i know it bro haha. I just post the post there. But i wonder if there is any chance to keep the CWM for S-On so everytime we flash a new rom, we no need to flash CWM again.

ghekua said:
i know it bro haha. I just post the post there. But i wonder if there is any chance to keep the CWM for S-On so everytime we flash a new rom, we no need to flash CWM again.
Click to expand...
Click to collapse
Flashing a new rom does not wipe cwm.
Cwm is always there unless you flash a different 'recovery'.
Sent from my Wildfire S using xda premium

...this is why people keep asking questions here. Please stop responding to these. Pleaseee?
Sent from my HTC-PG762 using Tapatalk 2

scott_doyland said:
Flashing a new rom does not wipe cwm.
Cwm is always there unless you flash a different 'recovery'.
Sent from my Wildfire S using xda premium
Click to expand...
Click to collapse
it's true for S-OFF bro. For S-On every time flash new rom need to fastboot to flash cwm again.
(i'd tried to install cwm by rom manager app, by flashable zip downloaded from clockworkmod website, no use)

I find downloading alquez's recovery and replacing the android_info file with the last RUU/update [of same], then flashing via hboot to be the simplest solution [since it works on marvel & marvelc].. I just keep that PG76IMG.zip on my sdcard and swapout android_info as needed [no need to sign or anything]. Of course then if you wanted latest-and-greatest [gsm] you'd root [Heritz guide works across board gsm & cdma], install your Rom Manager and reflash. But I like simple solution that works on both my wildfire s's
I do agree this is a general topic and if anyone has read my simplistic thread responses, I've stated above philosophy repeatedly in various threads.. and it seems to always work
Rob
Sent from my HTC_A510c using Tapatalk 2

ghekua said:
it's true for S-OFF bro. For S-On every time flash new rom need to fastboot to flash cwm again.
(i'd tried to install cwm by rom manager app, by flashable zip downloaded from clockworkmod website, no use)
Click to expand...
Click to collapse
How strange. I'm s-on and I never have to reflash CWM. I've only ever flashed it twice and the second time was just to upgrade to a later CWM.
Sent from my Wildfire S using xda premium

Upgrading to stock JB on Mac OSx

Got an Australian Gnex running 4.04. The OTS jellybean update is months away according to Vodafone AU so ive been looking into manual solution that causes the least disruption possible. Very tough diciphering the language on here. My apologies but there doesnt seem to be a specific thread that can help.
From what i have read - I can open the Bootloader and somehow flash the factory image without rooting?
Was on the dev page at google to get the latest firmware? - ive DL'd yakju Android 4.1.1 (JRO03C)
I have already unlocked the bootloader with a toolkit for mac found here on XDA. i just dont know what to do next? The file is a .tgz which ive never heard of? dont you normally copy the whole zip file to the SD card then boot into recovery and somehow flash the new firmware? Help.

bigdave78 said:
Got an Australian Gnex running 4.04. The OTS jellybean update is months away according to Vodafone AU so ive been looking into manual solution that causes the least disruption possible. Very tough diciphering the language on here. My apologies but there doesnt seem to be a specific thread that can help.
From what i have read - I can open the Bootloader and somehow flash the factory image without rooting?
Was on the dev page at google to get the latest firmware? - ive DL'd yakju Android 4.1.1 (JRO03C)
I have already unlocked the bootloader with a toolkit for mac found here on XDA. i just dont know what to do next? The file is a .tgz which ive never heard of? dont you normally copy the whole zip file to the SD card then boot into recovery and somehow flash the new firmware? Help.
Click to expand...
Click to collapse
All the info you need is in this post: http://forum.xda-developers.com/showthread.php?t=1626895

Petrovski80 said:
All the info you need is in this post: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Thanks - i had read that thread but im stuck at the directory commands. its not working on mac.

Did you download the proper platform tools for your OS?
Sent from my Galaxy Nexus using Tapatalk 2

Petrovski80 said:
Did you download the proper platform tools for your OS?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes. i dont know how use commands and directories. The thread is not clear for mac users.
The 'NEW!Install Stock Jelly Bean / Unroot to Stock Jelly Bean [Odin for Mac] ONLY GSM!' one click method didnt work.
Such a shame this has to be so complicated. Im stuck and now just have a wiped phone still on 4.04 and i cant ask any pertinent questions in the appropriate threads because im a new member.

Petrovski80 said:
Did you download the proper platform tools for your OS?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
bigdave78 said:
Yes. i dont know how use commands and directories. The thread is not clear for mac users.
The 'NEW!Install Stock Jelly Bean / Unroot to Stock Jelly Bean [Odin for Mac] ONLY GSM!' one click method didnt work.
Such a shame this has to be so complicated. Im stuck and now just have a wiped phone still on 4.04 and i cant ask any pertinent questions in the appropriate threads because im a new member.
Click to expand...
Click to collapse
Question remains - once the bootloader is unlocked - can you install the downloaded google factory image from recovery without any complex commands?

bigdave78 said:
Yes. i dont know how use commands and directories. The thread is not clear for mac users.
The 'NEW!Install Stock Jelly Bean / Unroot to Stock Jelly Bean [Odin for Mac] ONLY GSM!' one click method didnt work.
Such a shame this has to be so complicated. Im stuck and now just have a wiped phone still on 4.04 and i cant ask any pertinent questions in the appropriate threads because im a new member.
Click to expand...
Click to collapse
It is not complicated at all. If you don't know how to open a terminal window and type in commands, it has nothing to do with android or flashing. It has to do with knowing how to use your computer.
I already replied to you in the other thread: to switch directories in a terminal, you use the cd command, i.e., cd /this/is/where/my/files/are
Lack of knowledge on how to use your Mac should not be confused with anything Android... not related at all.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
It is not complicated at all. If you don't know how to open a terminal window and type in commands, it has nothing to do with android or flashing. It has to do with knowing how to use your computer.
I already replied to you in the other thread: to switch directories in a terminal, you use the cd command, i.e., cd /this/is/where/my/files/are
Lack of knowledge on how to use your Mac should not be confused with anything Android... not related at all.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I genuinely appreciate the help, but realise that 95% of computer users will never open a terminal and type a command. Ive typed your commands in terminal but its not working and i dont understand directories. If i dont ask questions ill never learn will i? I cant see your reply anywhere??

bigdave78 said:
I genuinely appreciate the help, but realise that 95% of computer users will never open a terminal and type a command. Ive typed your commands in terminal but its not working and i dont understand directories. If i dont ask questions ill never learn will i? I cant see your reply anywhere??
Click to expand...
Click to collapse
Asking questions if you don't understand is perfectly fine... and I'm willing to help. But complaining that a procedure is complicated and lengthy when it actually is not, is not cool.
As for your issue (although I've never used MacOS): if you save the files in a directory call junk, and junk is located in myname, the the command to reach junk would be something like: cd /myname/junk. Or, find a way to open a terminal in the junk directory to begin with -- I'm sure if you search any Mac help site (with something like how to open a terminal) you can easily find that out, no?
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Asking questions if you don't understand is perfectly fine... and I'm willing to help. But complaining that a procedure is complicated and lengthy when it actually is not, is not cool.
As for your issue (although I've never used MacOS): if you save the files in a directory call junk, and junk is located in myname, the the command to reach junk would be something like: cd /myname/junk. Or, find a way to open a terminal in the junk directory to begin with -- I'm sure if you search any Mac help site (with something like how to open a terminal) you can easily find that out, no?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The fact ive sat here for more than 4 hours reading through threads, searching forums, reading tech sites, asking friends, unlocking the bootloader, downloading firmware, trying desperately to make 'terminal' work with your method, and leaving posting in this forum as the last resort - is testmanet to how complicated this is to a new user - especially one on a mac system. Ive used one click root methods previously when i had access to windows - unfortunately i dont anymore. I think the guides are easy to follow as a PC user, not necessarily for a mac. Ive tried to use terminal to locate the files, i cant do it. dont understand the basic principals involved to understand the mistakes im making.

bigdave78 said:
The fact ive sat here for more than 4 hours reading through threads, searching forums, reading tech sites, asking friends, unlocking the bootloader, downloading firmware, trying desperately to make 'terminal' work with your method, and leaving posting in this forum as the last resort - is testmanet to how complicated this is to a new user - especially one on a mac system. Ive used one click root methods previously when i had access to windows - unfortunately i dont anymore. I think the guides are easy to follow as a PC user, not necessarily for a mac. Ive tried to use terminal to locate the files, i cant do it. dont understand the basic principals involved to understand the mistakes im making.
Click to expand...
Click to collapse
I think you are making it more complicated that it really is. When you open a terminal, in which directory does it open? In other words, what is the prompt that you see? THAT is the directory that you should download and extract all the files to.

That's the problem you need to fix. Read some basics about macosx. Get comfortable using it. Then proceed with flashing your gnex.
This looks like a good tutorial:
http://guides.macrumors.com/Terminal
Sent from my Galaxy Nexus using Tapatalk 2

I'm now rooted with super user acces. followed techfanatic9's guide in the Mac thread and keyed in the commands in terminal. But now how do i install the factory image from Google?Yakju-jro030c? Its not a rom is it??
Do i still need to learn terminal commands???

bigdave78 said:
I'm now rooted with super user acces. followed techfanatic9's guide in the Mac thread and keyed in the commands in terminal. But now how do i install the factory image from Google?Yakju-jro030c? Its not a rom is it??
Do i still need to learn terminal commands???
Click to expand...
Click to collapse
Another issue you are having is that you are trying too many different methods, and confusing them. There was no need to root if you are flashing a new rom.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Another issue you are having is that you are trying too many different methods, and confusing them. There was no need to root if you are flashing a new rom.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, so now there is no way i can do this because im rooted? ...im a frustrated, technically struggling user that just wants to try and get jelly bean stock image - nothing more extravagant than that. ive tried to follow every instruction to the letter.....aside from having to learn terminal language for OSx, im doing my best. come on dude, not everyone has that kind of time

bigdave78 said:
Okay, so now there is no way i can do this because im rooted? ...im a frustrated, technically struggling user that just wants to try and get jelly bean stock image - nothing more extravagant than that. ive tried to follow every instruction to the letter.....aside from having to learn terminal language for OSx, im doing my best. come on dude, not everyone has that kind of time
Click to expand...
Click to collapse
You can still flash the stock jb as per my instructions. It's just that rooting made no difference - it was a wasted step.
And as I said before, you don't have to learn the commands, as I've written them out for you. You just need to find out how to save the files and open a terminal in the same folder, which doesn't seem like a difficult thing to do. Google should be able to tell you how to open a terminal in a specific folder. Or, as I mention before, save the files in the folder which you already have your terminal open.
The whole purpose of my guide was to learn -- and you are have a more difficult time than others because you have taken shortcuts (I.e. 1-click methods) in the past.
I agree, not everyone has that kind of time: I have 3 kids (with everything that comes along with that), work a high-stress, 70 hour a week job, and no IT/tech/linux/android background, but I managed.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
You can still flash the stock jb as per my instructions. It's just that rooting made no difference - it was a wasted step.
And as I said before, you don't have to learn the commands, as I've written them out for you. You just need to find out how to save the files and open a terminal in the same folder, which doesn't seem like a difficult thing to do. Google should be able to tell you how to open a terminal in a specific folder. Or, as I mention before, save the files in the folder which you already have your terminal open.
The whole purpose of my guide was to learn -- and you are have a more difficult time than others because you have taken shortcuts (I.e. 1-click methods) in the past.
I agree, not everyone has that kind of time: I have 3 kids (with everything that comes along with that), work a high-stress, 70 hour a week job, and no IT/tech/linux/android background, but I managed.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I didnt find how to move the terminal command subject and i did try many different pages via google and many different ways of phrasing the query. So i just dumped all the files onto the desktop as that was where terminal seemed to be referringand it seems to be working. im waiting for the final reboot - its taking a long time. :fingers-crossed:

bigdave78 said:
I didnt find how to move the terminal command subject and i did try many different pages via google and many different ways of phrasing the query. So i just dumped all the files onto the desktop as that was where terminal seemed to be referringand it seems to be working. im waiting for the final reboot - its taking a long time. :fingers-crossed:
Click to expand...
Click to collapse
I think you got it! The first boot will take significantly longer than usually.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
I think you got it! The first boot will take significantly longer than usually.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Still waiting. should it take 15 minutes plus??

40 minutes. Stuck on the black screen with google and the lock at the bottom?
take it this is bad news.

[Q] Backup with no access to screen

Had a few questions here. I researched and found this tool. However, I can't post in the thread to ask questions because of my noobtasticness and I searched and couldn't find a similar problem elsewhere.
My first question is, can I use the root and backup tools in the toolkit with no access to the screen whatsoever? I damaged my phone and the touch and lcd screens aren't functioning, but I can plug it in and access memory via usb.
Secondly, I've received the replacement phone. Is there an order I should do all of this in? My first guess is to root/backup the old phone (if possible), then activate the new phone, then root/restore on the new phone. Does that sound about right?

aolbites said:
Had a few questions here. I researched and found this tool. However, I can't post in the thread to ask questions because of my noobtasticness and I searched and couldn't find a similar problem elsewhere.
My first question is, can I use the root and backup tools in the toolkit with no access to the screen whatsoever? I damaged my phone and the touch and lcd screens aren't functioning, but I can plug it in and access memory via usb.
Secondly, I've received the replacement phone. Is there an order I should do all of this in? My first guess is to root/backup the old phone (if possible), then activate the new phone, then root/restore on the new phone. Does that sound about right?
Click to expand...
Click to collapse
The phone with the broken screen isn't rooted already? If it is rooted this may help: http://forum.xda-developers.com/showthread.php?t=2353828

Cosmic Phoenix said:
The phone with the broken screen isn't rooted already? If it is rooted this may help: http://forum.xda-developers.com/showthread.php?t=2353828
Click to expand...
Click to collapse
Thanks, I found that thread too actually, but this phone isn't rooted. I was mainly contemplating root, if it's an option, as a way to take advantage of the more expansive toolset/backup options available to rooted phones in the toolkit. I just wasn't sure if rooting was an option for a phone with a broken screen.

aolbites said:
Thanks, I found that thread too actually, but this phone isn't rooted. I was mainly contemplating root, if it's an option, as a way to take advantage of the more expansive toolset/backup options available to rooted phones in the toolkit. I just wasn't sure if rooting was an option for a phone with a broken screen.
Click to expand...
Click to collapse
Oh, ok. I hope someone comes along to answer your question because now I'm curious... lol.
Edit: Also posted your link in that thread to possibly grab someones attention

Cosmic Phoenix said:
Oh, ok. I hope someone comes along to answer your question because now I'm curious... lol.
Edit: Also posted your link in that thread to possibly grab someones attention
Click to expand...
Click to collapse
Awesome, thanks. I checked on that post and someone responded about having usb debugging on...which I don't. So it looks like I may have to just do the straight backup without rooting unfortunately. :/

You don't need root to use my method, you just need a custom recovery...and remember NOT to boot into the system at all, only recovery or else the stock recovery will be reflashed
Sent from my S3 on Sense 5 (you jelly?)

CNexus said:
You don't need root to use my method, you just need a custom recovery...and remember NOT to boot into the system at all, only recovery or else the stock recovery will be reflashed
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
Followed the instructions on the post, and when I get to "./adb devices", I get "Permission denied" in terminal. This is with booting into recovery.

That means that the adb binary on your computer doesn't have executable permissions. Nothing to do with the phone.
Sent from my S3 on Sense 5 (you jelly?)

CNexus said:
That means that the adb binary on your computer doesn't have executable permissions. Nothing to do with the phone.
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
Ok, so tried this again, as I'm less familiar with terminal on my Mac than I am on my PC. Got my device discovered, twrp.img loaded into tmp. But when attempting to install I get a "/dev/block/mmcblk0p18: cannot open for write: Permission denied"

[Q] HELP!! Have I bricked my new device!? SO WORRIED!!

Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<

first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.

redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted

esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.

redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?

I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.

Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.

hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.

esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".

I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.

Help please. NEW to 2013 N7

Hello all. I am new to the N7. I look forward to trying out some of the awesome development in this forum. Before I begin I need to ask some things. I have spent ALL DAY today reading forums and researching this device b4 I begin. But to be honest, I can not spend days reading every post out there and still be a dad here. So I am trying to stream line this some. I am not a newbie in rooting / roming. Sorry if I have not seen a topic like this b4 posting. There are just so many in this forum now to go through. I will delete this one once helped if nessary. Also THANK YOU VERY MUCH in advance for any help I get here.
1. I have a Verizon note 2, Verizon PERMANENTLY locked the bootloaders on their phones so development has stoped/ slowed drastically. I know the N7 has a locked bootloader that can be unlocked. Is this still true on a stock 5.1.1 lollipop version? or Is there a step to reflash to an older rom I should do first?
2. I see the wugs toolkit out there and a nexus toolkit. Is there any reason to use one over the other? Are either of these working on my STOCK 5.1.1 rom still?
3. Can someone please run down the steps to achieve UNLOCK, ROOT, AND CUSTOM RECOVERY? I seen how wugs does all that in it's program. So if that is the way than a good link to use Please.
Once again. Thanks in advance for your help here. Please also feel free to add in here anything I need to be aware of b4 I begin making my N7 a beast of a tablet. I can not wait to try out some of the awesome roms and mods I have seen so far.
:thumbup::beer::thumbup::beer::thumbup::beer::thumbup::beer:
To root or not to root? That is the question.

1. It's unlockable
2. No need for a toolkit just use fastboot, unless you don't want to know what you're doing. It's in the platform-tools folder of the android sdk. There are many guides on xda about how to use it. Don't forget to install googles usb driver.
3. Very easy. Boot the tablet to the bootloader by holding volume down and power while turned off.
Plug into the computer and open a command prompt in whatever folder you have fastboot and type fastboot oem unlock and hit enter. Follow the steps on the tablet.
For recovery download the recovery .img you want and put it in the fastboot folder. Type fastboot flash recovery whatevername.img
To root just download the su zip from here and flash it through recovery.

You need to be careful you don't have a new Nexus 7 version which doesn't allow the mounting of any of the partitions in a custom recovery. I have one of these new Nexus 7s and no matter what I do I can't get the recovery to work, there's a thread about it.
Sent from my SM-G925F using Tapatalk

Batfink33 said:
You need to be careful you don't have a new Nexus 7 version which doesn't allow the mounting of any of the partitions in a custom recovery. I have one of these new Nexus 7s and no matter what I do I can't get the recovery to work, there's a thread about it.
Sent from my SM-G925F using Tapatalk
Click to expand...
Click to collapse
Ok so how do I locate n answer to this issue. The serial number in the bootloader info? Or something else?
Thanks for the two answers so far!
:thumbup::thumbup::thumbup::thumbup:
To root or not to root? That is the question.

robrooter said:
Ok so how do I locate n answer to this issue. The serial number in the bootloader info? Or something else?
Thanks for the two answers so far!
[emoji106][emoji106][emoji106][emoji106]
To root or not to root? That is the question.
Click to expand...
Click to collapse
Here's the thread on the issue. I bought my N7 yesterday and I'm affected by this. I can't resolve it and am stuck on stock at the moment which is annoying as I bought it to mess about with Roms and kernels. I'm not sure how you identify which tablets are affected but it seems the later manufactured ones are.
http://forum.xda-developers.com/showthread.php?t=3064562