EU 1/8 2100, list 4.
If I boot to recovery (hold both buttons), and select recovery (power), I get a dead android with 3 Chinese characters. Connecting to the MTK droid tool:
Code:
--->>> Connect to device <<<---
--- ERROR : --- TotalBytesPerChunk Not Found. Set default Page/Spare=2048/64 !!!
--- Unknown ROM structure, backup NOT possible!
--- ATTENTION! Recovery doesn't suit this phone!
--- Unknown ROM structure, backup NOT possible!
All I've done so far is add su using framaroot (and that seems to have been successful). ADB reboot works, adb shell gives file not found for /system/bin/sh
Yep. I'm on same version as you and also rooted with framaroot. I had the same thing. Waited a while, then pressed power button and it went into recovery.
When rebooting, it got stuck on the Omate screen. This is apparently normal and takes more than 10 mins but I got frustrated and did a battery pull. Had to reset permissions with SU cos it got messed up.
Also, go to settings > device > display > font size and make it small, cos Superuser screen will be larger than your screen and you can't easily give root permission (the buttons are off the screen)
Sent from my LG-V500 using XDA Free mobile app
LeighR said:
Yep. I'm on same version as you and also rooted with framaroot. I had the same thing. Waited a while, then pressed power button and it went into recovery.
When rebooting, it got stuck on the Omate screen. This is apparently normal and takes more than 10 mins but I got frustrated and did a battery pull. Had to reset permissions with SU cos it got messed up.
Also, go to settings > device > display > font size and make it small, cos Superuser screen will be larger than your screen and you can't easily give root permission (the buttons are off the screen)
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
I think you're describing something different... Installing SU was fiddly, but is covered under the 'do a factory reset' before reboot. I actually deleted one of the SU apks, and that cleared it. What I'm observing is that the shipped recovery image is unusable.
Well I tried to enter recovery and also I got the dead android with Chinese characters, so it sounds similar
Sent from my LG-V500 using XDA Free mobile app
Related
In order to install custom firmware on the Viewpad 7 and equivalent devices (Cherry Mobile Superion, Commtiva Linx N700, Olivepad VT-100, Spice MI700, and Camangi FM600) you must use an alternative recovery partition. There are several methods to accomplish this, but in this thread I will document what I use personally.
For starters ALWAYS create a backup of your original 'stock' firmware.
Rooting:
1. Download version 1.7 of Super One Click. Some users have reported issues with the latest version, but previous versions can be found in the thread.
2. Place your Android device into debugging mode, and connect to computer.
3. Right-click the Super One Click executable and select 'Run As Administrator'.
4. At program launch select 'rageagainstthecage' exploit method, then select 'Root'.
5. If there is no activity for more than 30 seconds and the terminal display is stuck at 'Running rageagainstthecage....' remove the USB plug momentarily and plug back in.
6. You should get the message “***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***” followed by an ADB reset, waiting for device, and finally a successful rooting message. (Apparently the looping issue is a known bug).
7. Once this process is complete your prompted to test the root condition. Follow the steps to verify.
Stock Backup:
1. Open up ADB shell within a terminal.
2. Get the list of partitions:
cat /proc/mtd
3. Pull each original partition from the device onto the SD card:
cat /dev/mtd/mtd3 > /sdcard/recovery.img (example...change for each partition)
Install Alternative Recovery Partition:
1. Copy the flash_image and clockwork recovery image to your SD Card (Find Attached Below).
2. Open a terminal (via computer or terminal emulator). Enter ADB shell.
3. Within ADB shell enter the following to change permissions for the flash_image:
chmod 755 /system/bin/flash_image
4. Replace the original stock recovery image by copying the clockwork image in it's place:
flash_image recovery /sdcard/cwrecovery.img
Installing Custom Firmware:
1. Copy the custom firmware of your choice to the SD card.
2. Power down your device.
3. Depress both volume keys simultaneously followed by holding in the power switch for a few seconds.
4. Upon power up you will see the birds logo and 'enter recovery' text in the top left corner of the screen.
5. Use the volume keys to step through the menu.
6. Select 'Backup & Restore' followed by 'Backup' to make a 'NANDROID' backup of the current firmware. The backed up ROM should be located in: /sdcard/clockworkmod/backup/date&time/
7. Once the backup process completes you will be back at the main recovery menu.
8. Select 'apply sdcard: update.zip.
9. Once complete select 'reboot device'.
DISCLAIMER: I cannot be held liable for anything you do to your Viewpad 7 (or equivalent device). Make sure you are comfortable with recovery tools, such as ClockworkMod, before proceeding.
[Reserved for Extras]
Installed, working ok. but the UP/DOWN button always jump 2 steps.
same. rooted. 2 spot jump on recovery menu. looks like pressing down moves one and then releasing the button goes another.
what custom rom works with the ViewPad7?
getting installation error Status (0) when I try tnt lite 4.4
Smilez said:
same. rooted. 2 spot jump on recovery menu. looks like pressing down moves one and then releasing the button goes another.
what custom rom works with the ViewPad7?
getting installation error Status (0) when I try tnt lite 4.4
Click to expand...
Click to collapse
TNT Lite is for the gTab.....NOT the Viewpad...therefore it will not work. There are only a couple modified ROMs available at this time for the Viewpad 7. I made a mod to stock ROM which can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=1008673
I believe there is someone else working on a Gingerbread ROM (as am I), but I don't know any details of they're progress.
As for the recovery menu navigation problem (moves two spaces instead of one), I think it came that way from the manufacturer (FIH). Not sure how to remedy it at this point.
Viewpad HELP!
Did the volume down + power by mistake
Now I have a message:
Power on with pressing VOLUME_DOWN keys to leave Auto-FTM
and then
Wrong Project!!!!!
Please Select project name:
FA0
FA1...
FST
Cant reboot... cant do anything...
Cant adb in
HELP !
Schilack said:
Did the volume down + power by mistake
Cant reboot... cant do anything...
HELP !
Click to expand...
Click to collapse
Hold down both volume keys and the power button, and then push in the reset button. Keep holding all the keys until you see 'Enter Recovery Mode'.
Smilez said:
same. rooted. 2 spot jump on recovery menu. looks like pressing down moves one and then releasing the button goes another.
what custom rom works with the ViewPad7?
getting installation error Status (0) when I try tnt lite 4.4
Click to expand...
Click to collapse
This is so far what I can find for CUSTOM ROM of VIEWPAD7.
http://forum.xda-developers.com/showthread.php?t=1008673
RC3.
James
May want to update the OP to reflect that one should be downloading SuperOneClick version 1.7, not 1.8. The latter doesn't include the RageAgainstTheCage exploit method and will not root the device.
Took me a few tries to get my new Viewpad 7 rooted, but it finally is.
second that...
chicknlil said:
May want to update the OP to reflect that one should be downloading SuperOneClick version 1.7, not 1.8. The latter doesn't include the RageAgainstTheCage exploit method and will not root the device.
Took me a few tries to get my new Viewpad 7 rooted, but it finally is.
Click to expand...
Click to collapse
I second that, took me a few tries also... Used SOC 1.7 and it was a bit confusing on my Win Xp (xp-home SP3) machine about VP7 drivers and its USB Mass storage state (should remove SD card in VP7 if you have it installed).
It finally worked when the " Synchronation Tool " was also installed and running off of the virtual "CD-Rom" that was installed when the VP7 is plugged in...
Anyways keep up the good work!!! Hope to see more updates/ROMs/mods/etc... for the VP7, I personally think its a solid device with the exception of the small internal storage it has...
Can anyone please help me? /system/bin/flash_image does not excist on my viewpad 7...
chicknlil said:
May want to update the OP to reflect that one should be downloading SuperOneClick version 1.7, not 1.8. The latter doesn't include the RageAgainstTheCage exploit method and will not root the device.
Took me a few tries to get my new Viewpad 7 rooted, but it finally is.
Click to expand...
Click to collapse
Thanks for pointing that out. At the time of writing the latest was 1.7. I will make the correction.
I have all the IMGs on sd card, how do i restore them to get the viewpad back to full stock
dazcox5181 said:
I have all the IMGs on sd card, how do i restore them to get the viewpad back to full stock
Click to expand...
Click to collapse
Have you installed an alternative recovery (like clockwork)? If so you will need to copy the original recovery partition over, and then copy the remaining original partitions over. You can perform these tasks using ADB shell, and by using flash_image for the recovery partitions. You can find more information on this with a quick search.
So...this might be answered in another thread, but since there's no subforum for this device, it's hard to tell, but I digress...
How do I get around the "jump 2 spots" issue when in recovery? I've got clockwork in there just fine now, but I want to back up my system before I do any more serious "playing" and since I can't ever get it to land on "backup and recovery", I'm not sure how to proceed. Thoughts?
chicknlil said:
So...this might be answered in another thread, but since there's no subforum for this device, it's hard to tell, but I digress...
How do I get around the "jump 2 spots" issue when in recovery? I've got clockwork in there just fine now, but I want to back up my system before I do any more serious "playing" and since I can't ever get it to land on "backup and recovery", I'm not sure how to proceed. Thoughts?
Click to expand...
Click to collapse
This double-step issue when navigating the recovery menu is definitely an annoyance. To get around it and only move one selection just keep the applicable volume key pressed down, and then hit the power button to choose the selection.
Sweet...got the backup going. Now just need to figure out how to partition the SD card and get link2sd working. Appreciate your help!
Sent from my SAMSUNG-SGH-I897 using XDA App
JRShield said:
Can anyone please help me? /system/bin/flash_image does not exist on my viewpad 7...
Click to expand...
Click to collapse
I have the same problem as well. Can anyone shed some light here? Please? I'm using CSL Droidpad Mi700 (essentially the same as Viewpad 7).
edit: just got through it. thanks. Now I flashed with CWM v2.5.1.2, but I can't navigate using the volume keys. The power button only give me blank screen... Help...
kuntilanak said:
I have the same problem as well. Can anyone shed some light here? Please? I'm using CSL Droidpad Mi700 (essentially the same as Viewpad 7).
Click to expand...
Click to collapse
You have to download the flash_image file from this thread (look in the first post), and copy it to your device.
This is what I'm getting:
Unable to chmod /system/bin/flash_image: No such file or directory
I'm stuck on this step.
So i have been stuck at the black screen for days. Searching online for answers and no luck. I am on the brink of just returning but i won't give up yet. So i got the new lg optimus v on black friday and rooted it. I installed busybox and superuser and clockwordmod. I put recovery from clockwordmod. Then being dumb at the time, i clicked factory reset. Now, i get black screen after the lg logo pops up. I look online and use androidscreencast. I use that to find out that i have recovery, but i can't see it because of those hittachi drivers. So, what i do is these instructions
Nandroid Instructions:
1) Extract the "BCDS-20110203-0357" file into the "nandroid" folder, under the "mem=477M" subfolder.
1a) For Clockwork Recovery, place the "BCDS-20110203-0357" file in /sdcard/clockworkmod/backup
2) Boot into recovery
3) Go into the "Backup/Restore" menu, and select "Nand Restore"
4) Allow it to restore
5) Reboot! System should be stock
6) Go below and flash stock recovery
Recovery Instructions:
1) Download flash_image and the stock recovery and nandroid back up
2) Extract stock recovery.img and flash_image to the root of your sdcard
3) Open up an adb shell, or terminal emulator on your phone
4) Enter the following codes:
flash_image recovery /sdcard/recovery.img
reboot recovery
right so now it worked. i then flashed a new rom i think. reboot and it works right? WRong. It loads up but I CAN"T SEE IT. I can hear the virgin mobile saying and androidscreencast shows me the android logo before crashing on me.
So i find out that i can do everything on it but can't see it. SO i go back to recovery with the 3 finger method. home + volume down + power. So then i decide to flash a new recovery.
So i go to adb. I type adb devices. IT shows my device and says its in recovery. Now i can't see it. So i try to use androidscreencast and it comes with an error.
Error attachment at the bottom for androidscreencast.
So i skip that and go back to adb. I try my last hope and try adb shell. Now that comes up with an error.
Error attachment at the bottom for adb shell issue.
Please if anyone could help with good detailed instructions. I don't want a link, some of those are super confusing. I need a good step by step instructions because i may be missing something and i don't know if that is the case.
EDIT: So i started with clockworkmod recovery menu some werid version. Then i put the recovery i was given here . Then after that i flashed this stock optimus v. The new recovery i flashed did not get rid of the black screen, i was still using android screencast. So, now when i boot up into "recovery" i don't know what to press or do and since android screencast + adb aren't there for me. I will have to do it blindly, but i need help.
Sorry to bump, but anyone help me?
To see if the recovery flashed right but isn't visible, boot into recovery, wait about one minute, press camera, then menu, then home. Depending on which recovery those are the select keys.
if the phone reboots after pressing those keys, the recovery works. Otherwise it didn't install right.
You can try
adb remount
Before
adb shell
to maybe get /system mounted for a shell prompt if recovery is broken.
Problems: the stock backup and recovery you flashed are for older ov's with a different screen driver, and stock recovery isn't rooted. Adb remount may not work unless you flashed the right stock zip.
bigsupersquid said:
To see if the recovery flashed right but isn't visible, boot into recovery, wait about one minute, press camera, then menu, then home. Depending on which recovery those are the select keys.
if the phone reboots after pressing those keys, the recovery works. Otherwise it didn't install right.
Click to expand...
Click to collapse
Ok i booted into recovery with the volume down + home + power button and let go when the lg logo popped up. I waited for 1 minute. I pressed the camera button first. No go , nothing happened. Then i pressed the home button (The button with the house on it). It then rebooted into android with the virgin mobile saying (I could hear it) So, recap I pressed home button and booted into black screen android couldn't see anything. Going to try adb when i get home.
TheRookie16 said:
Ok i booted into recovery with the volume down + home + power button and let go when the lg logo popped up. I waited for 1 minute. I pressed the camera button first. No go , nothing happened. Then i pressed the home button (The button with the house on it). It then rebooted into android with the virgin mobile saying (I could hear it) So, recap I pressed home button and booted into black screen android couldn't see anything. Going to try adb when i get home.
Click to expand...
Click to collapse
if it's stock recovery, adb will not work. if it's xionia recovery (might be, with the home instead of menu being select) you'll be ok with adb probably in recovery. if it won't work it'll say 'device not present' or 'connection refused.'
you'll probably have to turn on usb debugging blind in the blacked-out rom install to use adb to fix the recovery. Someone I helped with this some time back used a youtube video (here's the post) to find the right places to press on the screen to do that, then he was able to use android screencast to see recovery on his pc and fix it that way. if you can get debugging on, you can also use adb to fix it.
UPDATE: I did it. I turned on usb debugging with the black screen. I got android screencast and ddms. I can see the screen through android screencast. Now i have no root. So .
1. Root i want a good root for Lg Optimus V (New Screen Hittachi Screen)
2. How to flash working recovery that i can see . I want direct link to the recovery so i don't screw up.
3. How to flash working rom that i can see. Same thing direct link i ain't screwing up now.
4. How to flash a working stock Lg Optimus V New screen rom that i can use.
5. Do i need a new kernal or just working recovery???
nicely done.
you'll have to use screencast several times, then it'll get easier.
you'll need a few apps from market.
oi file manager to install apps from card.
flash_image gui to flash recovery
you need to check "allow install of non-market apps" under settings>applications
download gingerbreak 1.20.apk from here
copy it to your sd card. find it with oi file manager. click it and select install.
then run gingerbreak.
if you're lucky it'll work first try.
some people have had better luck using gingerbreak with the phone plugged into a pc.
it might take many tries if your phone is stubborn.
after it reboots, you can use flash_image gui to install this recovery
it's up-to-date and made to handle new or old screens.
then go to the iho thread herefor a gingerbread 2.3.7 rom, or Harmonia here
for froyo 2.2 rom.
both work without tweaking on your new screen.
both have install instructions in the linked threads.
after flash_image gui does it's thing you can turn off the phone and reboot into recovery
hold home+volume down, then hold power too, until after the silver lg logo goes away.
you could make a backup, it's normally advised.
use camera button to select.
good luck!
Thank you Very MUCH!!!!
One question about flashing the recovery. Can i use adb or some other method of flashing that recovery. Like say adb. I saw this somewhere wondered can i use this instead of flash_gui apk.
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
# flash_image recovery /sdcard/recovery.img
# reboot recovery
Just wondering, it would be easier for me.
Yes, definitely.
you'll need flash_image copied to the card like the recovery for that.
just change "recovery.img" to the actual recovery filename, or rename the recovery itself to recovery.img first.
Thank You agian very much! I got everything working and i am running CM 7.2. Very happy that i don't have get another phone. Very very helpful.
Hi just bricked my Archos 80 Cobalt whilst trying to root, followed instructions in [TUT Root Archos 80 Cobalt 4.0.4, however when I ran Runme.bat everything went smoothly until the Cobalt starting rebooting, the dialogue in command prompt window was stating "waiting for the device to show up again ..., however the Cobalt display initially showed the Archos logo for a few seconds then went blank. I waited 15 minutes without success.
I have subsequently tried to reboot the Cobalt numerously but always just get the logo followed by a black screen. I have tried to leave the device on charge for several hours (mains charger), and have also tried to reboot into recovery using vol- and usb, and vol- and power, always just get logo followed by blank screen Dialogue from command prompt window:
adb server is out of date. killing...
* daemon started successfully *
Pushing busybox....
3690 KB/s (1085140 bytes in 0.287s)
Pushing su binary ....
3065 KB/s (91980 bytes in 0.029s)
Pushing Superuser app
3719 KB/s (996704 bytes in 0.261s)
Making busybox runable ...
Please look at your device and click "Restore my data!"
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again....
Any help will be most gratefully received.
Is there a recovery menu for that tablet? The first 2 things I would try is to wipe data, and if it doesn't work, reflash/reinstall stock rom. I have gen9 101s, so I don't know much about that device.
Sent from my GT-I9100 using xda app-developers app
julle131 said:
Is there a recovery menu for that tablet? The first 2 things I would try is to wipe data, and if it doesn't work, reflash/reinstall stock rom. I have gen9 101s, so I don't know much about that device.
Unfortunately I cannot get it to reboot into the recovery menu, lots of research on the web and tried all sorts of button combinations without any joy
Click to expand...
Click to collapse
hmass said:
julle131 said:
Is there a recovery menu for that tablet? The first 2 things I would try is to wipe data, and if it doesn't work, reflash/reinstall stock rom. I have gen9 101s, so I don't know much about that device.
Unfortunately I cannot get it to reboot into the recovery menu, lots of research on the web and tried all sorts of button combinations without any joy
Click to expand...
Click to collapse
The rooting procedure doesn't affect the recovery partition. Enter recovery by holding volume down while powering on and keep holding until you see a broken android, then I think its volume up and power together. I can see by your first post that your tried that so a full recovery may be required.
The USB + Volume Down is for the rockchip recovery mode and you will need the driver in the recovery pack for that, you will see nothing on the screen when this happens.
If all else fails, within the rooting thread there is a recovery pack. Just download that and follow the instructions and the tablet will be fully restored to factory firmware.
Rest assured, its impossible to brick this device by rooting or any other firmware changes due to the nature of the platform. That doesn't rule out hardware failure tho and these are the not the highest quality tablets.
Click to expand...
Click to collapse
here is a rom that unbreaks the cobalt. http://www.arctablet.com/blog/featured/archos-cobalt-rooted-custom-firmware-2gb-storage-apps/
Sent from my GT-S5360 using xda app-developers app
Thanks every one for your help. I now know what I was doing wrong getting the device into recovery mode, other guides stated connect mains charger and then do the vol- and plug in USB cable trick, however won't work with mains charger connected, but it does work without charger connected.
Anyone else having the problem, the technique to get into recovery menu as stated above is:
Using the Hard Keys
-Shut down your tablet and disconnect if from the pc. Mains charger NOT connected.
-Press the volume key – (the one that lowers the volume)
-Insert the USB cable in the tablet while keeping pressed the volume button -
-Release the volume key
Thanks to gavroche and yousef8824, I have restored to factory, haven't tried the custom rom as the device was a gift for my sister and didn't have any more time to play with before needing to post. My wife has the same model, but haven't persuaded her to let me loose on it yet : ).
hmass said:
haven't tried the custom rom as the device was a gift for my sister and didn't have any more time to play with before needing to post. My wife has the same model, but haven't persuaded her to let me loose on it yet : ).
Click to expand...
Click to collapse
Personally until JB comes along with the various bug fixes there isn't a lot to be gained with the custom roms as the touchscreen reliability and wifi issues still remain.
I'm new to rooting and recently rooted my lg p769 , for the last 2 days i customized my launcher, added mods and themes. today i was deleting things i didn't need using the rootappdelete app and i accidentally deleted a .lge file immediately afterwards a few error boxes popped up and it rebooted and now will not go past my nyan cat boot animation , i tried the (vol down,menu,power button) combo to bring up recovery but the droid icon appears with a load bar then disappear and returns to the nyan cat boot animation which keep going without actually booting up the device , what should i do?
mike7djent said:
I'm new to rooting and recently rooted my lg p769 , for the last 2 days i customized my launcher, added mods and themes. today i was deleting things i didn't need using the rootappdelete app and i accidentally deleted a .lge file immediately afterwards a few error boxes popped up and it rebooted and now will not go past my nyan cat boot animation , i tried the (vol down,menu,power button) combo to bring up recovery but the droid icon appears with a load bar then disappear and returns to the nyan cat boot animation which keep going without actually booting up the device , what should i do?
Click to expand...
Click to collapse
Search and read...thats all u need to do
Dadovvv said:
Search and read...thats all u need to do
Click to expand...
Click to collapse
i have and i tried all of the manual button combos to bring me to the recovery screen and all have failed so far
Place the phone in upgrade mode and use the offline flash. But if you made cwm backup then just flash that.
Sent from my LG-P769 using xda-developers app. 'tis the season to give thanks so push the button already!
Nathan.7118391 said:
Place the phone in upgrade mode and use the offline flash. But if you made cwm backup then just flash that.
Sent from my LG-P769 using xda-developers app. 'tis the season to give thanks so push the button already!
Click to expand...
Click to collapse
is there a manual button combo to bring it to that becuase i cant get past boot animation
You'll need to turn off the phone. Then while holding volume up, plug in the phone to the computer. Upgrade mode should pop up.
Sent from my LG-P769 using XDA Premium 4 mobile app
This is the Fusion5 in question
https://www.amazon.co.uk/gp/product/B01CCYEIW2/ref=oh_aui_detailpage_o05_s01?ie=UTF8&psc=1
I tried rooting the tablet using kingoroot - both the Android app & the PC program..All 'failed' - but tablet was still running ok, so I'm guessing it's not possible to root it with these programs
Anyway, I accidentally left the battery to drain out, causing it to turn off - so started recharging it.
Once I thought it had enough charge I tried turned on the tablet, saw the White 'Fusion5' title screen followed by the black 'android' text screen... but now it's stuck on the android screen
So I've tried:-
> Turning off/on by power switch - same thing (White Fusion5/Black android screens)
> Press the small 'reset' hole on the back - same thing
> Tired different combo's of Power button/ vol +/vol - buttons - same thing
Have I bricked it ??
Is there a way to get the thing to boot up into recovery.. if so what's the button combo's ? or is there some other way using PC
IS there a recovery mode for this tablet or did kingoroot wipe it/corrupt it somehow ??
Any help greatly appreciated
EDIT: btw further searching seems to show theres a 'kingroot' and a 'kingoroot'
- but 'kingroot' website [https://kingroot.net] doesn't exist but a google search shows kingroot [https://king-root.net/] however the download is being picked up by Virus checker as malware
Has it booted far enough to retrieve a logcat?
If ADB is responding, adb reboot recovery is another hope.
qeexo said:
Has it booted far enough to retrieve a logcat?
If ADB is responding, adb reboot recovery is another hope.
Click to expand...
Click to collapse
Thanks for the quick reply however the main reason I went 'kingoroot' was for simplicity since I don't know anything about ADB
(I know of it, just not how to use it)
Anyway,tried following one of the many guides (this one in fact)
but when I do 'adb devices' it's not showing anything, although it's possible something is conflicting because even though my Samsung phone shows up when I plug it in, doing 'adb devices' shows nothing - I would've expected the Samsung to show up at least
I'll have more time during weekend to try & figure out why phone not showing in ADB & experiment with ADB a bit more