Disclaimers
- First of all: if you want to use clockwork or have the latest android releases, do yourself a favor and get a Nexus phone. Or, maybe, a OnePlus. In worst case scenario, go for freaking Samsung. Don't think Motorola, LG or anything else will make things easier. It won't.
- Well, I just spent a whole freaking day stuck in a few points which could have been made much simpler if there was a few points better explained in a lot of good other tutorials I've found along the way.
- But, at the same time, I honestly think writing in this forum is too dreadful (at least I could find no way to write with some markup). Only reason I'm doing this here is lack of a better place for good visibility positioning. In other words, so someone who might need this info can actually find it. Sorry if this offends anyone. It's about the same reason I believe in using eBay first to sell my used stuff instead of craiglist or dropbox. Most people who'd want "stuff" will look on eBay first.
- Here's the same guide in my "blog / forum" by the way.
A "bad guide", with no revisions
The main reference to me was, as one might expect, from cyanogen mod wiki.
The real steps needed are very similar:
1. Unlock device
2. Install recovery using fastboot
3. Wipe every single thing
4. Install CyanogenMod from recovery
All steps but 3 can be found on that wiki. Step 3 can actually become really big. Making it as clean as possible could be very complicated. Or very simple.
The most important thing is understanding the concepts of what's being done and knowing how long each step can actually take. Specially the ones that give no feedback. Such as that terrible horrible loading screen, which I've learned to hate. The "spinning CM robot" should appear for 1 or 2 minutes at most, but that's way too far from clear and that info is nowhere to be found.
I won't repeat the tutorial, rather I'll explain it and correct it.
Unlocking Device
This is for allowing your Razr to be tweaked. And it's not rooting the device as it may appear (being somewhat a newbie and not too interested in rooting, I've mixed up the concepts).
Other than this, the steps on the wiki are pretty clear and complete here, I don't see how anything could go wrong if you just follow it.
I've got no screen that would be more than a few seconds without a feedback.
Recovery and fastboot
This starts to present apparently minor issues.
It says to use Clockwork Mod but all newest files to download on the other wiki page itself already bring a Recovery Image. Now, CWM is well established and used, but the versions linked there didn't work on my device. Only the new Cyanogen Recovery works. And it's not as complete as, although I really appreciate the higher simplicity there. Anyway, in the end CWM is just not needed, a version I could find that loads can't install any ZIP and it ends up just holding back because it offers a lot of useless options.
And "Volume Down + Power" doesn't work to boot into recovery. At all. You need to hold Volume Up + Power, or some sort of combination from Vol Up & Down & Power. It's easier to just look for videos of how it's done. I can do it quickly most of the times using Vol Down & holding Power to boot into fastboot, and then just hold Vol Down and quickly hold power for 1 second, release, and keep holding Vol Up until a menu opens up in which you can choose to boot to Recovery (or back to Fastmode as well).
Those misleading things there held me back 1 hour at first... But the CWM really screwed me up big, wasting time trying to use it to fix stuff. It's just not enough. I guess.
Maybe, however, there's one thing it could prove to be important. Backing up. Install it for this, if you're worried about trying to recover data without using google's own backups, after android is installed. To me, that was more than enough.
I've got no screen that would be more than a half a minute without a feedback.
Wipe every single thing
`fastboot -w`. That's all that took me, although it did give errors and I still saw many warnings through the whole process, if only I knew this command before, it would have saved me 20 hours or so.
Maybe it was the sum of cleaning up stuff with CWM, but I doubt it.
I really don't want to get into more details here, right now.
I've got no screen that would be more than a few seconds without a feedback for anything I've done in this step.
Recovery for CM
You probably also want to install google apps. Just take the nano OpenGApps. And if you're trying to use CM stable and it bricks, just get the nightly build.
If you're lucky, installing with sideload should be enough. All those options are just means to getting the zip files into the device for recovery installation and if you'd only have to use sideload once it's perfect. Having to use it again eventually is a pain, because it doesn't save local copies on the device.
Another 2 options: You could also have a SD card to USB adapter, or use CWM mounting SD card and transfer everything through the USB cable.
The biggest missing information in this step, however, is this: the loading CM robot screen, which appears after you boot, when that wiki guide is over and it thinks "everything is fine". It should be not more than 2 minutes, from my experience.
But google says otherwise. You might be led to believe it could take many minutes, maybe as much as 10. Which can easily be extrapolated by "well, maybe it takes 15". Before you know it, you're easily wasting hours waiting for it.
So, there you go. Hope this might have been of any help to you! ;P
Related
I have a device that used to belong to a MSFT employee. At Microsoft you can just hand in your device and they will put a new ROM on it for you. So first thing I did when I got it is to HardSPL (OliNex 1.90) it and load up a new ROM (the one on it was a couple of builds back, and GPS didn't work etc.).
The strange thing is that ROMS seem to be 'loosing' files (as far as I can tell - apps won't open etc.) after a few days of otherwise great operation. If the device is rebooted, it's almost like a hard-reset; although the installation takes next to no time: and it gets stuck on the splash. Hard resetting the device makes it work for a few days more. The device didn't have these problems with the MSFT ROM (which I stupidly didn't backup).
I have tried a few ROMs and they all seem to have the problem:
MagicROM_23541_Sense25_Mar01
TAELROM_v4.23541_SENSE_2.5_28FEB10_LD
Timolol_5100207TH (awesome ROM)
So my current plan:
Flash stock ROM.
Flash stock SPL.
Flash stock ROM (hoping it will clear anything funny MSFT put on it).
Hard SPL.
Flash Timolol Stock-Like (seems to have the problems the soonest - 2 days max).
Does anyone have any other ideas?
Thanks guys.
I assume since you posted in the Touch Pro2/Tilt 2 section, that you own one of those devices. The roms you have mentioned below are (I believe) for a touch pro/fuze device. That could be your problem. Although, I would assume that you have one as I'm sure a rom for a different device would even flash to the device period. If you have the right rom/device combo and its a touch pro, then you should post in the thread for the roms. More details such as network and device will help the most.
Ah crap - the dangers of having too many tabs open. Can I move the thread myself?
moitoius said:
Ah crap - the dangers of having too many tabs open. Can I move the thread myself?
Click to expand...
Click to collapse
i moved it for you good luck at finding a solution
I don't think it's a hot idea to flash the stock spl. I'm not sure that it can be over-written with hard spl-you'll have to ask in the hard spl thread. If you do it, you might be stuck with the stock rom. Just try flashing the stock rom, then going to the custom one you want. That seems to work for a lot of people.
Farmer Ted said:
...Just try flashing the stock rom, then going to the custom one you want. That seems to work for a lot of people.
Click to expand...
Click to collapse
Thanks, that is significantly fewer steps . I will do that for now and report back in 2 or so days...
Small update - just flashed the latest stock Fuze ROM. Just before the customization app come up I saw that device.exe crashed... In any case, I will see what happens with the custom ROM.
You may need to reformat the memory of your phone. Having device.exe crash on a stock rom during bootup is kind of weird. I've never done it myself, but there are threads on it in the Leo forum. I wouldn't try the apps that they've put together, though. I guess you can search around for "Task 29" to find out how to do it properly.
Moved as not ROM Development.
@OP:
If the device was flashed on a regular basis, it's possible that the device flash memory is near end-of-life.
You could try running Raphael Diagnostics on it to see if that sorts it out.
HTH,
What is the lifespan (in terms of flashes) for a device like this?
Plus minus 2 days - it has been able to go as far as 5.
According to this post: http://forum.xda-developers.com/archive/index.php/t-514940.html
These are good options:
http://forum.xda-developers.com/showthread.php?t=435527
http://forum.xda-developers.com/showthread.php?t=491554
This one in particular: http://forum.xda-developers.com/showpost.php?p=3446141&postcount=16 (it applies to Rhodium, but people have had success with it).
Apparently Task 2a (equivalent of 29) is disabled on the OliNex 1.90 SPL - so I can't do a NAND format without reflashing the stock SPL (not that I would attempt that myself in any case ).
I'll run RaphaelDiagnostics and see if that comes up with anything.
Thanks for the help so far guys, I first want to see if the stock flash I did works (I smell a Wiki page).
I tried out the raphdiag-it's pretty cool. I've been having a few weird issues lately on my fuze. In particular, all of a sudden my boot-up time seems to have gotten slow (millisecond to idle thread went from 65-70 sec to 90-95 sec, and I hadn't messed with start up programs). Also, I have been having an issue with files on the main memory becoming corrupted, which has just been weird. Anyway, I ran an 'info 8' with mtty a few weeks ago, and it came up with 7 bad blocks, which seems normal. So, I ran raphdiag this morning, and ran the format nand routine. I was a little surprised, because after running it, I soft reset and the phone booted up normally like after a hard reset. I thought that it was going to wipe the entire rom memory clean, leaving only the radio, bootloader and splash screen. It didn't seem much different from a hard reset. The good news is that my startup is faster. With a setup I was using beforehand, the millisecond-to-idle-thread speed was 76 seconds, and after the format it was down to 71 seconds. However, I ran an 'info 8', and the memory analysis hadn't changed at all (same 7 bad blocks). I'm not sure if the formatting (task 29 or this) is supposed to clear that up, though.
I put both the raphdiag.nbh and a raphimg.nbh on the root of my normal 16 gb card. When you go into bootloader, it does a quick image update (takes about 2 seconds), then the screen tells you to push power for a rom update or push the action button to go into diagnostics. From there, you have maybe 4 or 5 choices. Scroll up and down with the up/down buttons, then push action. The first is a set of hardware tests, the second is something like 'run in/on', which appears to be a test scheduler. The 3d is the NAND format option, and I think the 4th and 5th options are 'calculate rom checksum' and then 'skuid', or something like that. To exit, I just soft reset, or used soft reset/vol down to go back to bootloader. After the format, I tried to flash (I think it called it re-flash), but it said there was no image present. You may need to do this on a clean card to get it to work (that is, format and then flash off the same card without swapping things out).
The diag tests are kind of cool. There's an auto mode that runs through all of them, but you have to do things to get it to work. The first is an LED test. The screen turns red, you stare at it for 5 min wondering what the hell is going on, then push the action button for the hell of it. Then the screen turns green. Push it a bunch more times, and it goes through shaded and checkered screens and whatnot, then it tells you it passed the test. There's a test for the slider, and you need to slide the keyboard in and out. The qwerty test was weird. It's configured for a touch pro (not a fuze), so I didn't know what the hell to do at first. The screen just says 'QWERTY_KBD_1', or something like that. I tried hitting the '1' button, and fn-1, and it did nothing. Then I just hit the top left button, and it said OK and prompted to hit 2. So, you just push all the keyboard buttons from left to right, top to bottom. There are also tests for the other hardware buttons, except for the 4 main buttons on the d-pad (home, back, send, end), which was kind of weird. If you think your power button or vol down button is effed, this tool will confirm/deny it for you.
Right, so the RaphDiag didn't brick your device. It's a bit risky - so I will first resort to less extreme measures - at least I know there is one success story.
I seriously wouldn't worry about it, but you may want to have a card reader available in case you need to remove raphdiag from you sd card to get a flash to work. It's possible that I didn't get the nand format to work properly, but I think I did it right, because the device definitely needed to cold boot. I was just surprised that there was still an OS there.
I'll take your word for it - BUT - in terms of gaining knowledge I am going to try the steps in the posts I found. If the NAND does need a format there is no doubt that I will land up doing it - but I will have first-hand experience.
This really needs a Wiki page once I am done; so I want to squeeze as much info out of the device as I can.
Can anyone else think of any gotcha's before I potentially brick it?
I ran the format a second time. It's really fast; it takes maybe 5 seconds. I haven't figure out how to exit from that part of the diag other than soft resetting, which leads to a cold boot. I'm surprised it's so fast. A hard reset takes about 30 seconds. I guess that it's working properly.
Farmer Ted said:
I ran the format a second time.
Click to expand...
Click to collapse
You are either very brave or very rich . Right, so here is hoping I have to go the final resort route - nothing yet though.
Hi All,
Disclaimer: I have scoured the internet and this forum looking for others who found solutions to my problem, and I've found several similar cases, but none quite like mine. I've done all I can think of short of sacrificing lambs on giant LG logos painted on the ground, so I'm resorting to posting. Forgive me if I missed something obvious - it's entirely possible since I'm still a newbie...
With that said, here's my issue:
I downloaded a CM7 nightly build and successfully flashed it on my p999 this morning using ROM manager. I went back to stock 2.2.2 afterward. Earlier this evening, I decided to flash CM7 again from the ClockWork recovery mode, but this time I didn't do a wipe (yes, I realize I'm a massive idiot). After rebooting, I got stuck in the standard boot loop with the cyan android alien doing its skateboard thing. I tried booting to recovery mode, but holding down power+down volume just brought up the android alien and the white box with a loading bar for a short time before rebooting. Standard suggestions involved (reasonably so) performing a hard reset. Though the phone won't boot straight into recovery mode, pressing the home button while the loading bar is visible brings up text suggesting the data, cache, etc of the phone are being formatted. After this process completes, I'm left at the system recovery utility with blue text and I can navigate the first menu, but the power button (nor any of the others for that matter) doesn't actually select any of the options. After removing the battery to reboot the phone, it still gets stuck in the boot loop and occasionally goes blank after failing to get to the launcher a few times.
I've also tried using the adb approach, but no device is detected on the linux machine despite being able to access some form of the bootloader.
Have I legitimately bricked my phone, or is there still something I haven't tried? Thanks a million for any help.
You didn't search very long did you? Go to the development section and find the thread on the one click nvflash tool, read the OP in that thread and you should be good to go.
G2X CM7
unusualparadigm said:
Disclaimer: I have scoured the internet and this forum looking for others who found solutions to my problem, and I've found several similar cases, but none quite like mine.
Click to expand...
Click to collapse
This forum is saturated with problems and cases exactly like yours, almost word for word.
G2X CM7
I found plenty involving a boot loop with CM7, but all of them were able to get to recovery mode just fine. Despite what you might think, I spent several hours trying to find something that worked. Thanks for the help. I'll see if nvflash helps.
They were able to get into recovery mode because they flashed it correctly using nvflash. Pardon my tone. I guess it sounds rude. Its been a long day and I'm tired. Anyway, nvflash recovery and you'll have no issues getting stuck like this.
G2X CM7
No problem. =) When trying to go the adb route, I saw the volume up+down trick to get the device to be detected, but it wasn't working on the linux or mac (lion - it's been having issues detects various external devices anyway) machines that I was using. After checking out the nvflash thread, it seems maybe a windows machine is necessary. Getting bootcamp going. Here's to hoping it'll work. Thanks a ton again for the suggestion - this is exactly what I was looking for (wanted a way to get CWM on the phone).
Make sure to check out this thread if you haven't already. Its a one click tool for nvflash.
http://forum.xda-developers.com/showthread.php?t=1056847
G2X CM7
Yay!
Thanks a ton! In retrospect, it seems my problem was right along the lines of multiple others', but I just didn't realize it since a few details on the specifics here and there seemed different. Sorry for wasting the board space, but thanks for your patience and help. I can't emphasize how much I appreciate it.
Hello,
I am posting in this forum for a few reasons.
First of all, I rooted my phone the day I bought it and took it home. I originally rooted it with a simple one-click method from a webpage I randomly found online.
Unfortunately, I do not remember the name of the hack, and I'm beginning to think that it has permanently affected the boot for my phone. After installing the hack, I found the CynoagenMod (or however it is spelled) custom ROM. I took some time into researching more about custom ROMs and installing with advanced settings, etc.
After I did my research, I found it best to flash with the new ROM and have had trouble with my boot since.
I did everything step by step from the website, and ran everything to the best of my abilities. The problem I am having now is that I can not access the HBoot menu.
In fact, every time I restart or shut off my phone, the screen goes black and will not respond to me holding down the recovery mode buttons. It stays pitch black and even battery resetting does nothing.
It will randomly turn on, vibrating for about a minute or two straight with the HTC splash screen, and then boot into my phone with the current ROM.
It seems strange that this is going on, and I have been searching all over the internet for weeks now trying to figure out what's wrong. I have reinstalled the stock RUU for my Inspire multiple times to no avail. It still sits at a black screen and will randomly boot into the splash whenever it deems to do so.
Is there anyone with any suggestions or advanced technical knowledge that could lead me to a solution? It is most unfortunate because I can't access for viewing s-on, s-off. I'm really debating whether to take the phone back to the rep and replace it. I'm just afraid they will discover the security off and tell me to suck a ****.
Thanks.
Run this nice little tool to factory reset, s-on your device
http://forum.xda-developers.com/showthread.php?t=1208507
Then reroot with the Hack Kit here. Read the "effen manual"
http://forum.xda-developers.com/showthread.php?t=952352
Thanks for the reply.
But here's my problem:
I can't access the HBoot menu in order to flash or install any type of file.
I've been using the terminal on my Mac to do most of my editing, and now I've ran in to a new problem: whenever I try to move files to my sd root, it says that the card is read only and therefore no files can be transferred to it.
I use the command ./adb push PD98IMG.zip /sdcard/
This is where I get the error.
Also, it takes my phone literally 5 or 6 minutes to boot into the splash screen after I use the command ./adb reboot bootloader/recovery (both of which I have tried).
I'm beginning to get quite frustrated, as I'm sure you can understand. I've also attempted to rewrite all of the necessary root programs onto the device in hope that the bootloader and recovery options will be accessible.
Do you have a solution for the write problem I am getting from my device?
Thanks.
Also, is there a way to go about doing this procedure straight from the Terminal since I can't run HBoot and recovery directly from my phone?
I have sucessfully restored s-on on my previous inspire so I can rma it for a signal issue I was having.
So I consider myself savy enough on this task. I rooted that inspire using a method available on here and not some random site. Doing that, u accept the possiblility that you may not get support on xda for using a root method that was not posted here. However, I do remember reading somewhere on here that certain inspires will go to a black screen at somewhere during the rooting process. My advice is to search the inspire threads for this topic, using keywords black screen, and see if this can provide a solution for you.
Sent from my HTC Inspire 4G using XDA App
Thanks soldier, but I've already searched through every black screen forum topic on this site for the inspire, all of which require reboot to HBoot, which I can not access from my phone without terminal access.
It seems like my phone is permanently soft bricked or something, or maybe the key commands don't do as they are supposed to. I can never get into the HBoot menu or recovery by holding down vol. - and the power button.
All it does is boots into the splash screen after about five minutes or son, and once the splash screen comes up, the phone vibrates for about 2 minutes straight.
During this time, my phone is not recognized by adp until after the phone stops vibrating.
I can't seem to find any forums ANYWHERE that propose a solution to this problem, let alone anyone that has the same issue as me.
Yeah that sux man. Well I would say, if you are within your warranty exchange, I would go that route first. Worst thing they can say is no. Although I still have yet to find a story about how someone was denied a warranty exchange for a phone that does not have physical damage. The next route is to suck it up and pay the deductible if you have insurance on it. (I always recommend insurance on any modern touchscreen smartphone) If that is not an option, then start saving up for a new phone, and lesson learned.
Ya, that seems like the only available option at the moment since my phone can't access HBoot even though I rewrote the root files to the device.
I just bought the phone this weekend, so I'm thinking of hard bricking the phone in case they decide to do an on-the-spot check. Hopefully they'll believe some bull**** story I can come up with and just give me a replacement.
Would any of you still recommend rooting again with a new phone? And what would be the best way to do so without the consequence of a soft or hard brick?
I'm just thinking of rooting and keeping the original stock OS on the device instead of running a custom ROM. That's what seems to have effed my phone.
All I really wanted to do was cut all the crappy useless programs and services out of the original Google Apps package with a fresh install to get the most out of my hardware.
FYI...if you haven't figured it by now, xda is the BEST site there is for android hacking/modding. This website IS the centralized location for all android developers/modders. Sure there are plenty of other android community sites out there, but this is the direct centralized source for all android hacking/modding.
My suggestion is to go ahead and root the next inspire you get using the hack kit in the development section. That is a long time proven and supported rooting method for the inspire. As far as roms go, from what you are saying, i would recommend you install a custom rom that is based on stock. (ex. Android Revolution) It was not the custom rom that effed up your phone, it was the questionable rooting method that did. Custom roms, by default, are superior to true stock roms, because they are modded, tweaked, and optimized far beyond the stock rom.
Awesome, I appreciate the information.
I'll keep that in mind. So which exact ROM would you suggest for my Inspire that's completely like Gingerbread?
I wasn't too fond of the CyanogenMod ROM because the GUI was a little sketchy. I like having a professional looking GUI, and I love the Gingerbread screens and menus.
Oh, one more thing. I had some success a little while ago getting into the HBoot menu from the terminal. Now I'm having a new issue:
I get into the menu at which the phone freezes and I can not use the arrow keys or power button to make a selection. Any tips?
I also believe that it is in fastboot, since it says fastboot at the top and has the Androids on the bottom skateboarding. Is this an issue? And am I screwed because I can't access the OS to turn the option off?
When you see the fastboot at the top of the screen and the androids skating at the bottom, that is perfectly normal. That is the pre screen before actually going into the bootloader. If your keys work, u press the volume down button to select which option you want, which will highlight in blue. The first option is the bootloader, so if you press the power button, it will load into the bootloader. The bootloader looks exactly the same as this screen, but with different options. This screen will show hboot at the top and have the options of fastboot, recovery, factory reset, simlock, and image crc. I have never heard of the keys not working at this point, so i couldn't help you there. Search around the forums if you haven't already.
If you want to compare this to something more familiar, think of these two screens as your motherboard bios to your PC. (What you see when your pc boots up, before it loads the OS, windows, mac, etc) On a pc, you can install any OS you want, like on the inspire, you can install any custom rom you want. But the motherboard bios is the highest level of permanent software that is directly written to the motherboard itself, like the bootloader/hboot is on the inspire. When rooting, you are essentially altering the motherboard bios on the inspire. When you install a custom rom, you are just installing an OS on the inspire.
There are plenty of custom ROMS that are based off of stock in the development section. I use and like Android Revolution. But when choosing custom roms, its always a matter of preference, and what works best for you.
digitalism said:
Thanks for the reply.
But here's my problem:
I can't access the HBoot menu in order to flash or install any type of file.
I've been using the terminal on my Mac to do most of my editing, and now I've ran in to a new problem: whenever I try to move files to my sd root, it says that the card is read only and therefore no files can be transferred to it.
I use the command ./adb push PD98IMG.zip /sdcard/
This is where I get the error.
Also, it takes my phone literally 5 or 6 minutes to boot into the splash screen after I use the command ./adb reboot bootloader/recovery (both of which I have tried).
I'm beginning to get quite frustrated, as I'm sure you can understand. I've also attempted to rewrite all of the necessary root programs onto the device in hope that the bootloader and recovery options will be accessible.
Do you have a solution for the write problem I am getting from my device?
Thanks.
Click to expand...
Click to collapse
It sounds like you may have the bad combination of a newer Inspire and the older ENG hboot. This is a problem dealt with commonly on the Aria/Inspire IRC channel. If you want to jump in, we can probably get you straightened out.
http://webchat.freenode.net/?channels=#liberatedAria
Awesome.
I am a little upset that I can't choose an action from the boot menu with the keys on the phone.
It also seems that the only way I can completely get into the boot menu is through the terminal after which I run ./fastboot-mac
After I put in this action, the menu will begin looking for the PD98IMG.zip file, and only goes on to say that there is no file, when there actually is one.
I just wish I could do all of this straight from the phone since I'm not well versed on terminal and commands for running programs to their full ability.
I wish I could figure out a way to the write permission on my sdcard so I could reinstall the .zip file for the bootloader to find.
digitalism said:
Awesome.
I am a little upset that I can't choose an action from the boot menu with the keys on the phone.
It also seems that the only way I can completely get into the boot menu is through the terminal after which I run ./fastboot-mac
After I put in this action, the menu will begin looking for the PD98IMG.zip file, and only goes on to say that there is no file, when there actually is one.
I just wish I could do all of this straight from the phone since I'm not well versed on terminal and commands for running programs to their full ability.
I wish I could figure out a way to the write permission on my sdcard so I could reinstall the .zip file for the bootloader to find.
Click to expand...
Click to collapse
You will not be able to use the volume rocker to select options if you have a PD98IMG.zip on your SD card.
Try booting into hboot with the SD card removed. That should let you move around the menu.
Sent from my Inspire 4G using the power of the dark side
Thanks for the heads up!
I can move the menus now.
Seems like all is going well now...
Just a matter of time.
digitalism said:
Thanks for the heads up!
I can move the menus now.
Seems like all is going well now...
Just a matter of time.
Click to expand...
Click to collapse
It's good to hear you're moving forward. Let us know how it comes out.
Sent from my Inspire 4G using the power of the dark side
Okay, this is my first time actually posting anything on XDA. I won't bother with an introduction and I'll just get to the meat of the issue. I am currently running CM 10.1 JB 4.3 with vincom's Superlite 4.0 (kudos to vincom btw, easily the best rom for this phone imo). Now, I know the problem is not related to the ROM as this exact same issue was occurring when I was running the Liquid Smooth ROM (I apologize I don't remember the dev for that one right now) and the Slimbean JB 4.2 ROM. Without fail, when I turn my phone off, restart it, whatever, it shows the Samsung logo for the appropriate amount of time, then goes to a blank screen. Zip, nada, nothing else. I've alowed it to sit for an entire night in such a state to see if it was just really slow. Still nothing. To make things stranger, when you hold down the power button to hard reset, the screen does the CRT monitor off animation... No clue why it manages that, but not to start up. Tried just tapping the power button when in this state and it still does nothing. I won't bother with logs unless someone truly wants them, but here's where things get really interesting (at least to me): I found that I can get the phone back up and running, and so far I've done this 50+ times and it's still a working method, but if I 3 button hard restart (or just 3 button power on) the phone to recovery, which for me is TWRP 2.6.3.0, there are no issues entering recovery. Then, after many many many trials and errors I found that if I make a recovery image for JUST the data (instead of the cache, android secure, etc etc), then flash the image for just that data, then tell the phone to reboot from within TWRP, viola! The phone boots up, no issues, no lost data, nothing. I would really just like to get this issue resolved . Sorry if this was more of a book to read than necessary, i'm just very confused and thought a detailed explanation would be best. Thanks to anyone for any leads, ideas, or suggestions!
apetwaffle said:
Okay, this is my first time actually posting anything on XDA. I won't bother with an introduction and I'll just get to the meat of the issue. I am currently running CM 10.1 JB 4.3 with vincom's Superlite 4.0 (kudos to vincom btw, easily the best rom for this phone imo). Now, I know the problem is not related to the ROM as this exact same issue was occurring when I was running the Liquid Smooth ROM (I apologize I don't remember the dev for that one right now) and the Slimbean JB 4.2 ROM. Without fail, when I turn my phone off, restart it, whatever, it shows the Samsung logo for the appropriate amount of time, then goes to a blank screen. Zip, nada, nothing else. I've alowed it to sit for an entire night in such a state to see if it was just really slow. Still nothing. To make things stranger, when you hold down the power button to hard reset, the screen does the CRT monitor off animation... No clue why it manages that, but not to start up. Tried just tapping the power button when in this state and it still does nothing. I won't bother with logs unless someone truly wants them, but here's where things get really interesting (at least to me): I found that I can get the phone back up and running, and so far I've done this 50+ times and it's still a working method, but if I 3 button hard restart (or just 3 button power on) the phone to recovery, which for me is TWRP 2.6.3.0, there are no issues entering recovery. Then, after many many many trials and errors I found that if I make a recovery image for JUST the data (instead of the cache, android secure, etc etc), then flash the image for just that data, then tell the phone to reboot from within TWRP, viola! The phone boots up, no issues, no lost data, nothing. I would really just like to get this issue resolved . Sorry if this was more of a book to read than necessary, i'm just very confused and thought a detailed explanation would be best. Thanks to anyone for any leads, ideas, or suggestions!
Click to expand...
Click to collapse
read the sticky right above ur post |READ THIS B4 POSTING | THE MOST Common Questions Answered HERE Q27
I'm trying to figure out a way to make a few edits to my system partition without unlocking my bootloader (no TWRP available anyways) and I found a setting to enable ADB in the STOCK Recovery.
I've been able to use it to sideload an app, but was wondering how to install an app to the system partition... without having to push the entire partition PLUS the added app....
does anyone know actual SPECIFICS about the boot options on the bootloader menu? I have managed to get stuck in some strange developer mode twice now, and am actually getting a little worried I'll royally mess this up.
One developer mode I booted into never loaded SystemUI- lock screen loaded the picture, never got any text (after 20mins waiting). Held power for a minute, device booted back into the bootloader menu.
the other developer mode I toggled somehow turned all my radios off on boot, turned them on one by one, notification CQOA or similar was starting up. Then a bunch of information in a text mode style flew across the screen on top of my desktop. Again, I held power down and got the heck outta there. I had to go back into bootloader menu and select Recovery and hit VolUp and Power to get a usable menu and then recovered from there.
all this exploring just has me curious as all hell what is possible through these menus. If I had another G7Power, I would be going as far down this rabbit hole as possible... but this is my only device at this time, so I am quite concerned I'll manage to break something and not recover....
at one point, using ADB in Recovery, I was able to get my ADB shell in root mode.... but I didn't realize the # meant root worked. And I haven't been able to get that working like that again.
EDIT: I still have the CMD window open from Friday night when I started this, otherwise I wouldn't have ever realized I had root for a few minutes in ADB
END EDIT
I want to make a few edits to build.prop without having to flash the whole partition.
My bootloader is LOCKED.
I literally just had an OTA last weekend.
am I being trolled by Moto on this? like, it looks like it is doing stuff, or COULD do stuff, but is actually nerfed? It seems like there has to be a secret key combo or something to get these menus to actually work.... it also looks like it is possible to switch to USERDEBUG if only for a single boot.
Any ideas are appreciated!
Dead_Dude said:
I'm trying to figure out a way to make a few edits to my system partition without unlocking my bootloader (no TWRP available anyways) and I found a setting to enable ADB in the STOCK Recovery.
I've been able to use it to sideload an app, but was wondering how to install an app to the system partition... without having to push the entire partition PLUS the added app....
does anyone know actual SPECIFICS about the boot options on the bootloader menu? I have managed to get stuck in some strange developer mode twice now, and am actually getting a little worried I'll royally mess this up.
One developer mode I booted into never loaded SystemUI- lock screen loaded the picture, never got any text (after 20mins waiting). Held power for a minute, device booted back into the bootloader menu.
the other developer mode I toggled somehow turned all my radios off on boot, turned them on one by one, notification CQOA or similar was starting up. Then a bunch of information in a text mode style flew across the screen on top of my desktop. Again, I held power down and got the heck outta there. I had to go back into bootloader menu and select Recovery and hit VolUp and Power to get a usable menu and then recovered from there.
all this exploring just has me curious as all hell what is possible through these menus. If I had another G7Power, I would be going as far down this rabbit hole as possible... but this is my only device at this time, so I am quite concerned I'll manage to break something and not recover....
at one point, using ADB in Recovery, I was able to get my ADB shell in root mode.... but I didn't realize the # meant root worked. And I haven't been able to get that working like that again.
EDIT: I still have the CMD window open from Friday night when I started this, otherwise I wouldn't have ever realized I had root for a few minutes in ADB
END EDIT
I want to make a few edits to build.prop without having to flash the whole partition.
My bootloader is LOCKED.
I literally just had an OTA last weekend.
am I being trolled by Moto on this? like, it looks like it is doing stuff, or COULD do stuff, but is actually nerfed? It seems like there has to be a secret key combo or something to get these menus to actually work.... it also looks like it is possible to switch to USERDEBUG if only for a single boot.
Any ideas are appreciated!
Click to expand...
Click to collapse
This is NOT the Q&A thread
fubugang said:
This is NOT the Q&A thread
Click to expand...
Click to collapse
I never said it was.
These menus appear to be useful for gaining access to various things. If a good source posted a response "these menus have already been scoured for any usefulness for people like us" I would leave it alone.
If I *was* to share my own experiences with what those various items can do, would you say this isn't the place to post that information? Please clarify- I honestly don't want to post on the wrong sub. Thank you.
Dead_Dude said:
I never said it was.
These menus appear to be useful for gaining access to various things. If a good source posted a response "these menus have already been scoured for any usefulness for people like us" I would leave it alone.
If I *was* to share my own experiences with what those various items can do, would you say this isn't the place to post that information? Please clarify- I honestly don't want to post on the wrong sub. Thank you.
Click to expand...
Click to collapse
As per the thread title: This thread is for development purposes only. All questions should should be asked in the Q&A thread
I dunno but I can tell you the SUPRA from cricket does not support bootloader unlock or root right now, and probably never will, I bought one but i will probably sell it off or gift it and buy the Power or G7 Plus with the money typically with moto you just go to the motorola bootloader unlock page enter your fastboot and type oem get_unlock_code or whatever it gives you a string you put it together and paste that in the moto bootloader page and they provide an unlocked bootloader boot.img you do get the code however when you put it in it gives you message that the phone cannot be unlocked thanks alot cricket, and Att I dont mind your service here but I want to be able to flash custom roms so I will just order a moto from swappa or straight from moto so i can do what I want with the phone, considering these are prepaid and you buy them out right it should not even be legal to keep the locked really, wish some attorney that had this stuff as a hobby would help us out it is flat out wrong to tell me I cannot unlock my bootloader its not like I owe anything on the phone thru cricket in the first place its paid for in full.