[Q] Kindle Fire System ro.product.board issue - General Questions and Answers

Okay I have a Kindle Fire that has been rooted with the Kindle Fire Utility and until recently everything was fine and worked great.
A few days ago I attempted to install an app from the Google Play store that was incompatible, and searched the internet for possible solutions of how to circumvent this incompatibility problem and came to a site that said to change the build.prop file on the kindle with the ES file explorer app.
From what I read it said that what I was going to do was "trick" the kindle into thinking it is a different device, like a Samsung Galaxy S2 that will run the app fine.
All said and done I changed a few lines in the build.prop file and reset the device, and notice there is a difference in how it looks, but the app still says incompatible. I take it upon myself to go back into the mentioned file and change a few more lines, and again reset the device.
This time it does not boot normally, but loops the kindle logo and ends with having a dimly lit background with nothing on it. I hold the power button only to have this repeat, and eventually make it to the fastboot screen and finally TWRP logo and screen.
I spent some time messing around with it only to get nowhere, when plugged into my computer that I used to root it, it will not recognize it as an ADB device.
I had my brother come mess with it because he tutors computer science from time to time and he did not seem to make much progress either.
The only difference from when I messed around with it and when he did is that now I cannot get to the TWRP screen like before my brother had it. I asked him if he was able to change anything, and he said the only thing he did was when resetting it with the power button, instead of choosing recovery to go to the TWRP screen he just let it boot normally, which before never interfered with getting to the TWRP screen.
If anyone knows what I have done or can do to reverse this or even restore it to factory settings or back to when it was rooted, I would appreciate it greatly.
And if I left any details out, I can try to fill in any blanks.
Thanks!

Related

[Q] Can't Access HBoot, Random Startup

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

Fighting a lost cause?

I've got a rooted (Super SU, but the original root manager was Superuser) LG C800 that I was having problems with. To be specific, I installed some apps on to the system. Some of these apps would be Titanium Backup for root, Avast Mobile Security, ROM Tool Box Lite, Super SU, and a quite a few others. From day one they seem to be kicked right back to my S.D. card, but not all at the same time, and some would stay on the system. I read where I should move the apps back to my S.D. card and try to re-install them on the system minus the data. When I did, the phone went nuts. Now it stays in a restart mode but never fully boots up. Can I salvage it, and if so, please tell me how?! I have tried the hard reset/recovery boot where you hold down the power button, volume, and a few other keys, but it did not work. I'm a broke college student and can't really afford to buy a new phone. I used this one for everything including tethering it to get my assignments done at home and turned in on time. Please help! I'm open to suggestions....... My phone will be completely off. When I plug it into my computer, via U.S.B., it automatically turns it on whether I want it to be on or not. Then it starts off in "reboot recovery" mode, will boot all the way to the point to where the home screen would normally turn on, but then it starts in that "boot loop" all over again but never fully boots up before going back to the beginning of that "boot loop" yet again. I can't even get it to register on my laptop as being plugged in. The reason I took the apps I placed on the system off was because sometimes when I'd re-boot the system the apps would be on the system and sometimes back on my S.D. card without my involvement of any kind other than rebooting my phone. Is completing a Nandroid recovery or re-installation of my ROM even possible with my computer no longer recognizing it as even being plugged in? From what I can tell it won't be. Am I fighting a lost cause or is it salvageable?
Rooted myTouch Q 4G, a.k.a. LG C800
I believe it has a 2.3.4 GRJ22-perf, and then something like 2.6.35.7? I can't remember off the top of my head, and I can't pull it up on my phone anymore or else I'd double check.
Have you tried booting into recovery?
(More about my phone from the original post) Honestly.........I'm not what you may consider technologically inclined. I have however done about as much research online concerning this matter as any one person can do. I've looked it up on all major sites, and many smaller ones too, that post remedies for phone, or "human" if you'd rather, malfunctions. They all talk about still being able to reach a home screen or doing the whole holding the power and volume decrease buttons until I "reboot recovery" screen appears (if that's what you're referring to as doing a recovery reboot as). Don't forget the one where you hold hold the power and volume decrease buttons along with the "A" and "F" keys as well. I even tried one from here where you're supposed to push the genius button after the Android figure leaves the screen. My phone won't allow me to do either. Basically if it's online, I myself, or this girl that's been staying with me, have tried it without any results. On the initial boot the Android figure and the box with the arrow coming out of it show up and it boots until just about the point that it use to switch over to the home screen and it will start the whole "boot loop" over again. The thing is though that the Android figure and box aren't there any other time after the first boot, and with every boot loop it makes after that, the time is reduced from the beginning of the loop to the end when it starts all over again. The phone won't shut off unless I remove the battery and even though my laptop no longer recognizes the device, when I plug my phone into it or another power source and it's off, it automatically turns itself on and begins that boot loop all over again. there is one thing I have yet to try. I read on one site where I could download a custom ROM on my S.D. and then try reboot it, but it never makes it to the point in which the files on my S.D. card are ran, much less scanned. I am still 100% open to any and all suggestions in the diagnosis of this issue. I may record and place a video on one of the more popular "tube" sites to better show or further explain what's happening and then come back on here to post the link?! Feel free to reply back if it's possible you can help before I'm able to complete that later this evening. And thanks for any and all help in advance to everyone.

[Q] AT&T LG G2 All files erased, Twrp wont mount, please help

So heres the story....wife has had lg g2 since it came out with 0 issues. About 3 days ago the phone starts doing some crazy ****, flipping through screens by itself, opening and closing apps, deleting things, rebooting, changing system settings. This was after earlier in the day she had downloaded some random games for my son to play (not sure if this was the cause/is at all relevant, just trying to be as detailed as possible).
My first though was that one of the games may have had some virus/malware **** going on, so did a factory reset. The reset was successful, however the issues continued. Next though was to root/unlock/install custom rom. (I have done this to all my phones, with minimal issues, so i felt fairly confident in doing so) So i rooted, installed twrp 2.7.0.0, and flashed this rom - ATT-stock-rooted-D80020K.zip - and all seemed well. Phone booted and behaved normally for the rest of the day (12 hours or so). Plugged in charger, went to sleep.
Next morning, wake up, grab phone, and its showing the LG logo (like when you first power it on). Restart (power button long press) and it boots into TWRP, and i go looking for the rom file to reflash, and its gone. All files are gone. In the file explorer in TWRP, i can see the files,(data, system, boot, and so on) but when i click on them there in nothing in any folder. All downloads gone. Everything.
But i can still get into TWRP, so i thought ok, ill just plug into pc, mount the phone, copy appropriate files, reflash rom, and all will be good. WRONG. I cannot get TWRP to mount the phone, and at this point ive got a pretty expensive paperweight.
All my unlock/flash/root experience has been on HTC devices up to this point, and i have never had an issue like this.
If anybody can advise what to do next, Im listening. Ive exhausted my knowledge on the subject at this point and NEED HELP PLEASE.
Thanks in advance.

Need assistance/info with bricked shield tablet

Received a shield tablet through a promotion my company was doing with nvidia, decided to try it out. (pointing this out ahead of time to let the 'just return it' people know that I cant and am stuck with it.) upon finally deciding to boot it up a couple months later, it booted into the bootloader menu instead of booting like normal. then when choosing to boot would boot into a very stripped version of android with few apps, tegra services repeatadly crashing, no app store/play/etc . I wanted to have the proper out of the box experience nvidia intended, so decided to hunt down a stock factory image to flash to it to just resolve the issue and start from scratch with my new tablet. was able to flash recovery/boot/system/userdata/etc via fastboot. upon restarting, screen went black and wouldnt start. plugged in to computer, device manager says "APX" and that's it. with unknown device/driver icon. if I power it off all the way and plug it back in it just goes back to saying "APX" with a "?" in device manager.
how can I get it out of this mode and booting so I can finally try this thing out? have tried diff combos including bootloader/recovery mode button presses at boot time and nothing works, goes back to the same thing. I've also seen mention about nvflash and some other things when looking into this, but nothing solid on where I get the program, how im supposed to use it to fix my device.
Thanks

Galaxy S6 with a broken screen, used dr fone, now it's possibly bricked, what to do?

Hi,
I've recently broken my S6 by accidentally smashing the screen - it completely died as a result, the screen went black with a single green line on it at first, which then procceeded to disappear as well. I figured that I wouldn't bother repairing it since it isn't much cheaper to replace the screen than to buy a new one. But now I kinda want to do that since I can get a used screen for cheap. The problem is, before I knew that I had attempted to recover my data from the phone and succeded. The phone doesn't have root which makes things harder, but I did a little research on the subject and used a program called dr fone to do that, but since it asks you to pay up in order to actually pull your data from the phone (it only shows you your photos/calls etc., doesn't let you transfer it without paying) I thought to myself **** that and tried to cheat a little. Well basically the program asks you to put your phone in download mode I believe (it tells you to hold down home+power+volume down) and then uploads something to it that lets you use adb freely - although it doesn't really tell you that, so while it was uploading the thing I found adb in the program folder and entered the pull command to transfer the data onto my PC. While I was doing that dr fone was "uploading" something to my phone and got stuck at 90%. I honestly had no idea what I was doing but I succeeded in getting my data and didn't think twice about what I should do next so I unplugged the phone with the program still being stuck on 90% progress.
Now the phone doesn't seem to react to anything I do, it doesn't turn on, the LED doesn't flash (it did before) and I have no idea if it's able to enter recovery because the screen is dead and holding down any combination of buttons doesn't seem to work unless I'm doing something wrong.
What I would like to know is whether I ****ed up something badly without replacing the screen because I don't want to purchase one for a phone that will possibly refuse to work anyway. Is there any way to figure that out?

Categories

Resources