Database Develop

Need Help please [solved] !!!

I have Imilika's AOSP ICS ROM V6,
I changed the buid.prop
ro.sf.lcd_density=213
for tablet mode. after I reboot, my GNote is not booting. I cannot go to recovery mode or download mode.
Please help. I don't know what to do

Got it
OK, I was really sad about what happens to my phone, but finally I managed to fix it .
As I told you, my phone was not booting to recovery or download modes (key combinations not worked). finally I try to connect to PC via USB and luckily my PC could detect my phone . So i realized that the problem is the display not coming but phone is halfway booted.
So, I tried to change my build.prop via adb but failed due to cannot grant root permission (becoz display is off).
Finally I issue a adb commad to reboot in recovery mode.
"adb reboot recovery"
yeah, that command directly take me to the CWM recovery. then I flash AOSP v6 again.
Now, my phone is working again.
P.S. I just note this down for others if they get same problem future !

I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!

priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
If you don't know what ADB is, you probably shouldn't be flashing so regularly. Anyway, ADB stands for "Android Debug Bridge" and it is a protocol for device control, development, and debugging.
Sent from my GT-N7000 using Tapatalk

priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
adb is a connection type. we can run shell commands (in the phone), file transfer via adb by using our PC. for that we should have to enable usb debug mode in our mobile.
Actually you might used adb, when you root your phone in the first place . If you have CF-Root zip file, just extract it. you will see a folder called "files", in there you can see adb.exe .
If you need test run,
connect phone via USB(make sure you've enabled USB debug), open command prompt, navigate to that "files" directory.
run "adb shell ls" (to run "ls" command in phone)
run "adb push <anyfile in the PC> /system/sdcard/" (copy files from PC to sdcard)
like that

OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..

priyanv said:
OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..
Click to expand...
Click to collapse
Its functionality is not only to copy files from pc to mobile and vice versa.You can use it to get logs due to bad flashing,zip align apps,reboot into recovery,DL mode,normal reboot etc...

[Q] ADB Sideload isn't working for me!

Hello there
I am stuck without a ROM and without a ROM zip file anywhere on the internal device that I can use TWRP to install. The only option I have at the moment is to use adb sideload, and this is my first time doing so.
I downloaded this:
adt-bundle-windows-x86_64-20130522
Anyway, I am trying to follow this tutorial but it's not working out for me:
http://forum.xda-developers.com/showthread.php?t=2317986
It looks simple and easy, but this is the problem I am facing:
"I changed directories to where the adb.exe is (inside platform-tools) and ADB Sideload is already started in TWRP. However, whenever I type "adb devices" it only says "List of attached devices" and nothing under it. Whenever I try flashing the ROM, it says error: device not found. What am I doing wrong here? I even changed the name of the ROM to rom.zip to make it shorter as per a suggestion in the first page of the thread, but that didn't work either."
Can someone please help me and tell me how to make it work? I have been without a ROM for hours waiting for the SDK to download this my internet is pretty slow. Thanks a lot!

Okay now I realize my device isn't actually recognized, although it works fine with fastboot usb.
What do I do? I tried having windows automatically search for drivers but it didn't find anything.

Okay after doing some more reading I realized I never actually opened SDK Manager, and when I try, it just opens a black command prompt window and then shuts down. I then came across this article and realized I need Java JDK drivers before I can actually run SDK Manager and then follow the rest of the tutorial. Maybe that is the problem??

You need HTC drivers , if you didn't install HTC SYNC, open "virtual CD", that appears at connection of phone with PC and you will see folders with drivers for different OS.

Thanks, mate. I already fixed the problem but I forgot to update this thread. You are right, I did not have the proper drivers, so I downloaded and installed HTC Sync Manager and then everything went great.

I had the same problem last night trying to flash my first rom ever, but thankfully i had a usb otg cable that I used to put the rom zip in my flash drive and flash it into the phone

TarekElsakka said:
Hello there
I am stuck without a ROM and without a ROM zip file anywhere on the internal device that I can use TWRP to install. The only option I have at the moment is to use adb sideload, and this is my first time doing so.
I downloaded this:
adt-bundle-windows-x86_64-20130522
Anyway, I am trying to follow this tutorial but it's not working out for me:
http://forum.xda-developers.com/showthread.php?t=2317986
It looks simple and easy, but this is the problem I am facing:
"I changed directories to where the adb.exe is (inside platform-tools) and ADB Sideload is already started in TWRP. However, whenever I type "adb devices" it only says "List of attached devices" and nothing under it. Whenever I try flashing the ROM, it says error: device not found. What am I doing wrong here? I even changed the name of the ROM to rom.zip to make it shorter as per a suggestion in the first page of the thread, but that didn't work either."
Can someone please help me and tell me how to make it work? I have been without a ROM for hours waiting for the SDK to download this my internet is pretty slow. Thanks a lot!
Click to expand...
Click to collapse
Just get the all in one tool, ins;tall the relevant drivers and then go to recovery and select sideload a rom, go to the all in one toolkit and select sideload a rom, then choose the rom, simples
Sent from my Transformer Prime TF201 using xda premium

Thanks, guys. I ordered an OTG USB cable this morning just to avoid any future problems.

[Q] Help! Wiped system without ROM on card. How to USB mount in TWRP?

I just loaded a new version of CM 10.1 on my sdcard ready to flash. I rebooted in TWRP, did the necessary wipes, then went to install my new ROM. Surprise, using Safari on Mac, it automatically opened the downloaded .zip file to a folder I didn't realize this as I was transferring, so now I have the extracted folder for my ROM, but the system can apparently only read .zips. So I am now without an OS. And no, I don't have a backup on the card. I just transferred it to my Hard Drive a few days ago to save on storage. But now I am VERY clear why it should stay on the card. Stupid.
I noticed that TWRP has a USB mount feature so I could copy over the proper .zip. But it won't mount on my computer (Mac or PC). In the console I see "E:Unable to locate volume information for USB storage mode." I tried getting into it via ADB, which worked before, but now it does not even list my device. Tried ADB side load, and it just never starts up on the Kindle.
I could never get fastboot to detect the device in the first place, so I haven't even bothered with any of that.
What can I do? All I want is to get my .zip back on the kindle. Or is there a way to .zip the extracted folder back into a .zip on the kindle itself with command line? Is there a way to install folders instead of .zips?
I've scoured several similar posts but nothing seemed to be resolved, or their fixes depending on ADB working.
Please help!

There isn't a way to re-zip a directory within Android in such a way that it can be flashed in recovery. You'll need to sort out your driver issue in Windows, or use the Mac (better choice anyway) to 'adb push' a new ROM to your sdcard.
Did you happen to wipe your internal storage before this happened?

soupmagnet said:
There isn't a way to re-zip a directory within Android in such a way that it can be flashed in recovery. You'll need to sort out your driver issue in Windows, or use the Mac (better choice anyway) to 'adb push' a new ROM to your sdcard.
Did you happen to wipe your internal storage before this happened?
Click to expand...
Click to collapse
When I did my wipe, I just followed the same instructions as when I did my original flash. Wiped system first, and then did the Factory Reset which includes data, cache and dalvik.
I tried plugging in the Kindle to my Mac while TWRP had the USB mounted, but nothing. I was just using the Android File Transfer for Mac that Amazon originally recommended when I first got it. That does not recognize anything now. Is there another way to access a Kindle on a Mac? Can you get Android SDK and run from a Mac Console command line? I thought all the commands were only for Windows. Does the Mac work better?
For my PC, I had the ADB drivers working fine before this. When I plug in now, I hear the windows SFX and it shows up in device manager as "Other Device" but listed as a Kindle. But the driver doesn't work, and it can't find drivers when I search. The Kindle used to show up as its own device with Android ADB under it. That never shows up anymore, probably why I can't do ADB commands.
But I think the computer is fine, because when I try to reinstall those drivers, it says they are already there. I'm guessing the Kindle itself is not allowing it to be recognized because there is no way to "enable ADB" in its settings since the OS is gone. I was hoping TWRP would have this built in.
I'm not sure why ADB Sideload doesn't work. It just sits there forever trying to start. I wish I could just push a new .zip that way. It's driving me nuts trying to figure out why nothing ADB works after the wipe.
Thanks

I downloaded the SDK for Mac and ran the ADB commands through Mac Terminal — it recognized the device! I never would have thought to try the Mac. Not sure why it worked differently, but it did. I was able to push a new ROM .zip through ADB and all is well.
Still not sure why I couldn't get the TWRP USB mount to work, but I learned my lesson, always keep a backup ON-CARD.
Thank you!

jhonny0099 said:
I downloaded the SDK for Mac and ran the ADB commands through Mac Terminal — it recognized the device! I never would have thought to try the Mac. Not sure why it worked differently, but it did. I was able to push a new ROM .zip through ADB and all is well.
Still not sure why I couldn't get the TWRP USB mount to work, but I learned my lesson, always keep a backup ON-CARD.
Thank you!
Click to expand...
Click to collapse
I assumed you already tried it on the Mac. But yeah....Mac is waaaaaay better at detecting the Kindle Fire than Windows.

[Q] HELP: Can't Get TWRP to Mount/Possible Brick

First off, I apologize in advance for this post considering that there might already be one that could answer my question. I'm in such a **** storm right now and I don't have time to do a search.
I installed a ROM on the phone in preparation for shipping it to someone who just bought it. I then went back into TWRP recovery (version 2.5.0.0) so that I could wipe out all my data/information that was still on the phone (things like backups, picture files, etc). Like a complete IDIOT I wiped everything, even the OS.
I see an option to mount in TWRP (so I can push a ROM onto it) but either I'm not doing it correctly or it won't work unless done using USB OTG. I found a reference here: http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/ saying that I could mount it via a usb cable connected to my computer. So again, maybe I'm just doing something wrong.
Bottom line, am I doing something wrong and if so what? OR, can this only be fixed using USB OTG mounting? If that is the case could someone point me in the right direction for doing so with this phone.
BTW, I also tried installing the RUU file but no dice with that either. Basically get an error that it can't connect to phone.

The easiest way it to RUU(but you said you can't get it to connect)
Try this
(If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Any other questions shoot me a PM

Thanks much! Everything worked out once I did what you suggested. I was able to sideload the ROM and all is swell.
Sent from my Nexus 5 using xda app-developers app

[Q] Sensation XL bricked after factory defaults.

Hi,
Like many, I got the same problem after installing new ROM (Runymede KitKat 4.4), but even after reading many threads and advises in other sites, my phone is still bricked. Any help will be highly appreciated.
Details:
Loaded the ROM, was working, but no internal SD.
I was stupid enough to perform a factory default, then, being even more stupid (amazing, no?), deleted the ROM somehow.
Now I'm left with a brick which only accepts recovery mode, nothing else.
Phone is connected to a PC, with working cable (verified), but not recognized by PC.
When I enter the recovery, in FASTBOOT mode.
Same screen gives me the following:
******IR-KEY***
RUNNYMEDE PVT SHIP S-OFF (yes, I'm sure it's off)
HBOOT-6.25.444
RADIO-3831.16.00.16_M
eMMC-boot
Oct 20 2011.00:20:33
Now, I managed to go to recovery, and browse there in file manager.
Went to system/etc/ in order to check vold.fstab, but it's not there.
Went to SDcard directory - no ROM zip file is there (of course. I deleted it...).
Bottom line - 1 Sensation XL stuck on boot, no ROM or installed system, no recognition by PC = nice paper weight.
The recovery I'm getting is TWRP (not CWM) and as I wrote, it's on S-off.
It's quite clear to me that first step is to somehow load a ROM.zip file to the device, but as I wrote - it's not recognized by PC (Yes, I did try to do USB mount via TWRP. No, it did not help. nothing recognized, even after replacing USB port and even on a different computer).
Tried few "magic tools" that meant to save HTC XL found in the web, no help. Youtube search brought me few guides, but all start at working device with working ROM installed, while mine has nothing.
Next (last?) was to try and transfer the zip file via ADB sideload, and here I got stuck:
Downloaded different kinds of ADB packages I found, but I don't understand how to use them. I'm not using LINUX/UNIX or any similar based OS, but MS WIN7. I assume that it needs to be done via CMD window, but couldn't find
a proper guide of how to try and transfer the file to the device. all guides seem to assume that I know what I'm doing, while (as result proves) I have no clue.
I'l be really thankful if someone can publish a dummy-proof, step-by-step guide for using ADB sideload method to identify the device, then transfer a new ROM to it.
Any other suggestions would be welcomed as well, unless it's something like "hold firmly, move your hand back and throw the piece of sh&$t on the nearest brick wall" or "paint in light Blue, drive to nearest beach and throw as far as you can".
Thank you for lasting the long post, and even more if you can suggest a solution.

dnt wrry
shemer_t said:
Hi,
Like many, I got the same problem after installing new ROM (Runymede KitKat 4.4), but even after reading many threads and advises in other sites, my phone is still bricked. Any help will be highly appreciated.
Details:
Loaded the ROM, was working, but no internal SD.
I was stupid enough to perform a factory default, then, being even more stupid (amazing, no?), deleted the ROM somehow.
Now I'm left with a brick which only accepts recovery mode, nothing else.
Phone is connected to a PC, with working cable (verified), but not recognized by PC.
When I enter the recovery, in FASTBOOT mode.
Same screen gives me the following:
******IR-KEY***
RUNNYMEDE PVT SHIP S-OFF (yes, I'm sure it's off)
HBOOT-6.25.444
RADIO-3831.16.00.16_M
eMMC-boot
Oct 20 2011.00:20:33
Now, I managed to go to recovery, and browse there in file manager.
Went to system/etc/ in order to check vold.fstab, but it's not there.
Went to SDcard directory - no ROM zip file is there (of course. I deleted it...).
Bottom line - 1 Sensation XL stuck on boot, no ROM or installed system, no recognition by PC = nice paper weight.
The recovery I'm getting is TWRP (not CWM) and as I wrote, it's on S-off.
It's quite clear to me that first step is to somehow load a ROM.zip file to the device, but as I wrote - it's not recognized by PC (Yes, I did try to do USB mount via TWRP. No, it did not help. nothing recognized, even after replacing USB port and even on a different computer).
Tried few "magic tools" that meant to save HTC XL found in the web, no help. Youtube search brought me few guides, but all start at working device with working ROM installed, while mine has nothing.
Next (last?) was to try and transfer the zip file via ADB sideload, and here I got stuck:
Downloaded different kinds of ADB packages I found, but I don't understand how to use them. I'm not using LINUX/UNIX or any similar based OS, but MS WIN7. I assume that it needs to be done via CMD window, but couldn't find
a proper guide of how to try and transfer the file to the device. all guides seem to assume that I know what I'm doing, while (as result proves) I have no clue.
I'l be really thankful if someone can publish a dummy-proof, step-by-step guide for using ADB sideload method to identify the device, then transfer a new ROM to it.
Any other suggestions would be welcomed as well, unless it's something like "hold firmly, move your hand back and throw the piece of sh&$t on the nearest brick wall" or "paint in light Blue, drive to nearest beach and throw as far as you can".
Thank you for lasting the long post, and even more if you can suggest a solution.
Click to expand...
Click to collapse
here i will help you...
first of all jst go to recovery, as you said it is twrp, then select mount option and again select mount storage and your pc will open up dialogue box which will be your sdcard...
if this FAILS....then go to wipe option, select advanced wipe and jst tick on sdcard option and click on repair drive......you will see sdcard details...
try it..
if you get any details of sdcard then reply me...

Hi.
Thanks for the reply.
I forgot to mention, did try the "mount" option, including wipe every option (separately and combined).
Still no sign from PC.
Micro USB port is good, I get charging of battery and PC responds when phone is connected, but looks like driver is corrupted or missing.
I'm pretty sure my only option is ADB sideload. Once I get the zip file on the phone, looks like I can proceed from there...

download htc driver
shemer_t said:
Hi.
Thanks for the reply.
I forgot to mention, did try the "mount" option, including wipe every option (separately and combined).
Still no sign from PC.
Micro USB port is good, I get charging of battery and PC responds when phone is connected, but looks like driver is corrupted or missing.
I'm pretty sure my only option is ADB sideload. Once I get the zip file on the phone, looks like I can proceed from there...
Click to expand...
Click to collapse
then you only need to download new htc driver and use windows xp if win7 fails...
other option is go to device and printers in win7, > right click on your android device device icon > troubleshoot it.... i think everything will be fine...
and if this will help then you are able to mount usb storage from mobile twrp recovery...

nirmalviper said:
then you only need to download new htc driver and use windows xp if win7 fails...
other option is go to device and printers in win7, > right click on your android device device icon > troubleshoot it.... i think everything will be fine...
and if this will help then you are able to mount usb storage from mobile twrp recovery...
Click to expand...
Click to collapse
Hi,
HTC driver (included in HTC sync) downloaded, no change.
Unfortunately, WIN XP is not really available...
The Android device is not there, that's exactly the problem.

Hi,
An update regarding this HTC.
I put it in my friend's lab, he found that the USB port connection was loose, so after some welding it's working, and phone is identified by the computer.
Managed to send it a ROM zip file, then flashed the ROM, phone is functioning, but...
Problem now is that the phone's internal memory (what HTC define as "SD card", although it's the internal flash memory) is still not found by the phone - e.g. impossible to take photos, get any files with whatsapp or any other storage related actions.
I did try to install another ROM, same result.
I think problem is derived from the fastboot version, which is (still):
******IR-KEY***
RUNNYMEDE PVT SHIP S-OFF
HBOOT-6.25.444
RADIO-3831.16.00.16_M
eMMC-boot
Oct 20 2011.00:20:33
Every former thread I saw in XDA or other site, related to 1.25.0 or 1.28.0 (ICS or JB), not this HBOOT.
Note that phone is in S-OFF, but memory is not yet found.
TWRP is installed, of course (so phone is already rooted).
IMHO, what I should do is replace the HBOOT version, but I have no clue of how to do so.
Found some old threads about this issue, but either the download links are broken, or the "tool" package in the link is disabled by Chrome browser due to trojan warning.
Would much appreciate if any of you can assist with clear step-by-step guide of what should be done in order to "save" the SD memory of the phone, as I could not find any proper guide even after spending much time searching.
Thanks in advance
Shemer.